Systems and methods for performance data streaming, performance data file reporting, and performance threshold monitoring

ABSTRACT

In an example method, a management service (MnS) producer sends a first request to establish a connection for streaming performance data regarding a wireless communications network to a MnS consumer. The MnS producer receives a first response from the MnS consumer confirming establishment of the connection, and streams one or more units of performance data to the MnS consumer sequentially using the connection. The one or more units include one or more performance metrics regarding the wireless communications network. The MnS producer sends a second request to the MnS consumer to terminate the connection, and receives a second response from the MnS consumer confirming termination of the connection.

CLAIM OF PRIORITY

This application claims priority under 35 U.S.C. § 119(e) to U.S. Patent Application Ser. No. 62/855,220, filed on May 31, 2019, the entire contents of which are hereby incorporated by reference.

TECHNICAL FIELD

This disclosure relates generally to wireless communications networks, such as cellular networks. More specifically, this disclosure relates to techniques for transmitting performance data regarding a wireless communications network.

BACKGROUND

Wireless communication systems are rapidly growing in usage. Further, wireless communication technology has evolved from voice-only communications to also include the transmission of data, such as Internet and multimedia content, to a variety of devices.

SUMMARY

In an aspect, a method includes sending, by a management service (MnS) producer, a first request to establish a connection for streaming performance data regarding a wireless communications network to a MnS consumer; receiving, by the MnS producer, a first response from the MnS consumer confirming establishment of the connection; streaming, by the MnS producer using the connection, one or more units of performance data to the MnS consumer sequentially, the one or more units including one or more performance metrics regarding the wireless communications network;

sending, by the MnS producer, a second request to the MnS consumer to terminate the connection; and receiving, by the MnS producer, a second response from the MnS consumer confirming termination of the connection.

Implementations of this aspect can include one or more of the following features.

In some implementations, the connection can be established according to a WebSocket protocol.

In some implementations, the one or more performance metrics can include at least one of a latency associated with at least a portion of the wireless communications network, a throughput associated with at least the portion of the wireless communications network, a number of registered subscribers for at least the portion of the wireless communications network, a number of established network sessions for at least the portion of the wireless communications network, or an energy efficiency of at least the portion of the wireless communications network.

In some implementations, the one or more performance metrics can include at least one of a number of attempts to perform a particular operation with respect to at least a portion of the wireless communications network, a number of successful attempts to perform the particular operation with respect to at least the portion of the wireless communications network, or a number of unsuccessful attempts to perform the particular operation with respect to at least a portion of the wireless communications network.

In some implementations, at least one of the first request or the first response can include a Hypertext Transfer Protocol (HTTP) GET command. The GET command can include an indication to upgrade the connection from an HTTP connection to a WebSocket connection.

In some implementations, streaming the one or more units of performance data can include sending one of more WebSocket Data frames sequentially. The one or more WebSocket Data frames can include the one or more units of performance data to the first MnS consumer.

In some implementations, the one or more units of performance data can be included in the payload data of the one or more WebSocket Data frames.

In some implementations, the payload data can be encoded according to Abstract Syntax Notation One (ASN. 1).

In some implementations, at least one of the second request or the second response can include a WebSocket Close frame.

In some implementations, the method can further include receiving, by the MnS producer, a subscription request from a second MnS consumer; and subsequent to receiving the subscription request, transmitting, by the MnS producer, one or more notifications to the second MnS consumer according to the subscription request. The one or more notifications can include one or more second performance metrics regarding the wireless communications network.

In some implementations, the notification can be transmitted using a HTTP POST command.

In some implementations, the subscription request can include an indication of a threshold value with respect to the one more second performance metrics. The one or more notifications can be transmitted responsive to the one more second performance metrics crossing the threshold value.

In some implementations, the wireless communications network can be a Fifth Generation (5G) network in accordance with 3rd Generation Partnership Project (3GPP) technical standards.

Other implementations are directed to systems, devices, and non-transitory, computer-readable media having instructions stored thereon, that when executed by one or more processors, cause the one or more processors to perform operations described herein.

The details of one or more implementations are set forth in the accompanying drawings and the description below. Other features and advantages will be apparent from the description and drawings, and from the claims.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a block diagram illustrating an example wireless communication system.

FIGS. 2-3 is a block diagram illustrating an example architecture of a system including a core network.

FIG. 4 is a block diagram illustrating an example of infrastructure equipment that can be included in a base station, user equipment, or both.

FIG. 5 is a block diagram illustrating an example computer platform that can be included in user equipment, an application server, or both.

FIG. 6 is a block diagram illustrating example baseband circuitry and radio front end module circuitry.

FIG. 7 is a block diagram illustrating example cellular communication circuitry.

FIG. 8 is a block diagram illustrating example protocol functions for implementing in a wireless communication device.

FIG. 9 is a block diagram illustrating example components of a core network.

FIG. 10 is a block diagram of an example computing system for executing executable instructions.

FIG. 11 is a block diagram of an example management architecture of mobile networks that include virtualized network functions

FIG. 12 is a block diagram of example of a management services architecture.

FIG. 13 is a block diagram of example of 5G management services.

FIG. 14A is a block diagram of an example management service.

FIG. 14B is a block diagram of an example management service and related management service components.

FIG. 15 is a block diagram of example management capability exposure governance.

FIG. 16A is a block diagram of an example management function.

FIG. 16B is a block diagram of example scenarios of consumption of management services by management functions.

FIG. 17 is a block diagram of an example service based architecture for management data analytics.

FIG. 18 is a block diagram of an example management data analytics service.

FIG. 19 is a block diagram of an example management data analytics service.

FIG. 20 is a block diagram of an example deployment model of a management data analytics service.

FIG. 21 is a diagram of an example process for transmitting performance data regarding a wireless communications network.

FIG. 22 is a block diagram of an example resource structure of a performance data file reporting service.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION

This disclosure describes methods and systems for transmitting performance data regarding a wireless communications network.

In an example implementation, a management service producer can monitor the performance of a wireless communications network, and generate performance data based on the monitoring. As an example, the performance data can include information such as the latency associated with the wireless communications network, the throughput associated with the wireless communications network, a number of registered subscribers for the wireless communications network, a number of attempts to perform a particular operation with response to the wireless communications network, and/or any other type of information regarding the wireless communications network.

Further, the management service producer can transmit at least some of the generated performance data to one or more management service consumers. In some implementations, the performance data can be streamed to the one or more management service consumers using a protocol that provides for full-duplex communications channels, such as WebSocket, rather than a protocol that only provides for half-duplex communications channels, such as Hypertext Transfer Protocol (HTTP).

In some implementations, the management service producer can also make at least some of the performance data available for retrieval on demand, and report the availability to one or more management service consumers. In response, the one or more management service consumers can initiate the retrieval of some or all of the available performance data from the management service producer.

In some implementations, the management service producer can also transmit notifications to one or more management service consumers when the performance of the wireless communications network satisfies certain conditions. Accordingly, the management service consumers can be quickly notified of any changes to the condition of the wireless communications network, and in response, can perform one or more appropriate remedial actions in a timely manner.

The methods and systems described herein can provide specific technical benefits in the field of computers and wireless communications systems. As an example, in at least some implementations, computer systems can exchange performance data regarding a wireless communications network more quickly, efficiently, and reliably (e.g., compared to computer systems that example performance data using other protocols, such as HTTP). Accordingly, the computer systems can perform operations using fewer computer resources (e.g., less processing power, less network bandwidth, etc.), thereby increasing the effective capacity of the computer systems. Further, this enables the computer systems to be deployed in resource constrained environments, thereby enabling the computer systems to be used in a wider array of situations and use cases.

Further, in some implementations, the methods and systems described herein can be used in conjunction with one or more wireless standards, such as those specified by Third Generation Partnership Project (3GPP) technical specifications. In some implementations, the methods and systems described herein can be used to transmit performance data that was generated in accordance with those standards.

A system (e.g., the systems described in relation to FIGS. 1-20, below) can be configured to implement one or more of these embodiments either individually or in any combination. These embodiments are subsequently described in greater detail with respect to FIGS. 21 and 22.

FIG. 1 illustrates an example architecture of a system 100 of a network, in accordance with various embodiments. The following description is provided for an example system 100 that operates in conjunction with the long-term evolution (LTE) system standards and 5th generation (5G) or new radio (NR) system standards as provided by 3GPP technical specifications. However, the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3GPP systems (e.g., Sixth Generation (6G)) systems, IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), or the like.

As shown by FIG. 1, the system 100 includes UE 101 a and UE 101 b (collectively referred to as “UEs 101” or “UE 101”). In this example, UEs 101 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as consumer electronics devices, cellular phones, smartphones, feature phones, tablet computers, wearable computer devices, personal digital assistants (PDAs), pagers, wireless handsets, desktop computers, laptop computers, in-vehicle infotainment (IVI), in-car entertainment (ICE) devices, an instrument cluster (IC), head-up display (HUD) devices, onboard diagnostic (OBD) devices, dashtop mobile equipment (DME), mobile data terminals (MDTs), Electronic Engine Management System (EEMS), electronic/engine control units (ECUs), electronic/engine control modules (ECMs), embedded systems, microcontrollers, control modules, engine management systems (EMS), networked or “smart” appliances, MTC devices, M2M, internet of things (IoT) devices, and/or the like.

In some embodiments, any of the UEs 101 may be IoT UEs, which may include a network access layer designed for low-power IoT applications utilizing short-lived UE connections. An IoT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), ProSe or device-to-device (D2D) communication, sensor networks, or IoT networks. The M2M or MTC exchange of data may be a machine-initiated exchange of data. An IoT network describes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections. The IoT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the IoT network.

The UEs 101 may be configured to connect, for example, communicatively couple, with a radio access network (RAN) 110. In embodiments, the RAN 110 may be a next-generation RAN or a 5G RAN, an E-UTRAN, or a legacy RAN, such as an evolved universal-terrestrial RAN (UTRAN) or GERAN. As used herein, the term “NG RAN” or the like may refer to a RAN 110 that operates in an NR or 5G system 100, and the term “E-UTRAN” or the like may refer to a RAN 110 that operates in an LTE or 4G system 100. The UEs 101 utilize connections (or channels) 103 and 104, respectively, each of which includes a physical communications interface or layer (discussed in further detail below).

In this example, the connections 103 and 104 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a GSM protocol, a CDMA network protocol, a PTT protocol, a POC protocol, a UMTS protocol, a 3GPP LTE protocol, a 5G protocol, a NR protocol, and/or any of the other communications protocols discussed herein. In embodiments, the UEs 101 may directly exchange communication data via a ProSe interface 105. The ProSe interface 105 may alternatively be referred to as a SL interface 105 and may include one or more logical channels, including but not limited to a PSCCH, a PSSCH, a PSDCH, and a PSBCH.

The UE 101 b is shown to be configured to access an AP 106 (also referred to as “WLAN node 106,” “WLAN 106,” “WLAN Termination 106,” “WT 106” or the like) via connection 107. The connection 107 can include a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 106 would include a wireless fidelity (Wi-Fi®) router. In this example, the AP 106 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below). In various embodiments, the UE 101 b, RAN 110, and AP 106 may be configured to utilize LWA operation and/or LWIP operation. The LWA operation may involve the UE 101 b in RRC_CONNECTED being configured by a RAN node 111 a-b to utilize radio resources of LTE and WLAN. LWIP operation may involve the UE 101 b using WLAN radio resources (e.g., connection 107) via IPsec protocol tunneling to authenticate and encrypt packets (e.g., IP packets) sent over the connection 107. IPsec tunneling may include encapsulating the entirety of original IP packets and adding a new packet header, thereby protecting the original header of the IP packets.

The RAN 110 can include one or more AN nodes or RAN nodes 111 a and 111 b (collectively referred to as “RAN nodes 111” or “RAN node 111”) that enable the connections 103 and 104. As used herein, the terms “access node,” “access point,” or the like may describe equipment that provides the radio baseband functions for data and/or voice connectivity between a network and one or more users. These access nodes can be referred to as BS, gNBs, RAN nodes, eNBs, NodeBs, RSUs, TRxPs or TRPs, and so forth, and can include ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). As used herein, the term “NG RAN node” or the like may refer to a RAN node 111 that operates in an NR or 5G system 100 (for example, a gNB), and the term “E-UTRAN node” or the like may refer to a RAN node 111 that operates in an LTE or 4G system 100 (e.g., an eNB). According to various embodiments, the RAN nodes 111 may be implemented as one or more of a dedicated physical device such as a macrocell base station, and/or a low power (LP) base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.

In some embodiments, all or parts of the RAN nodes 111 may be implemented as one or more software entities running on server computers as part of a virtual network, which may be referred to as a CRAN and/or a virtual baseband unit pool (vBBUP). In these embodiments, the CRAN or vBBUP may implement a RAN function split, such as a PDCP split wherein RRC and PDCP layers are operated by the CRAN/vBBUP and other L2 protocol entities are operated by individual RAN nodes 111; a MAC/PHY split wherein RRC, PDCP, RLC, and MAC layers are operated by the CRAN/vBBUP and the PHY layer is operated by individual RAN nodes 111; or a “lower PHY” split wherein RRC, PDCP, RLC, MAC layers and upper portions of the PHY layer are operated by the CRAN/vBBUP and lower portions of the PHY layer are operated by individual RAN nodes 111. This virtualized framework allows the freed-up processor cores of the RAN nodes 111 to perform other virtualized applications. In some implementations, an individual RAN node 111 may represent individual gNB-DUs that are connected to a gNB-CU via individual F1 interfaces (not shown by FIG. 1). In these implementations, the gNB-DUs may include one or more remote radio heads or RFEMs (see, e.g., FIG. 4), and the gNB-CU may be operated by a server that is located in the RAN 110 (not shown) or by a server pool in a similar manner as the CRAN/vBBUP. Additionally or alternatively, one or more of the RAN nodes 111 may be next generation eNBs (ng-eNBs), which are RAN nodes that provide E-UTRA user plane and control plane protocol terminations toward the UEs 101, and are connected to a 5GC (e.g., CN 320 of FIG. 3) via an NG interface (discussed infra).

In V2X scenarios one or more of the RAN nodes 111 may be or act as RSUs. The term “Road Side Unit” or “RSU” may refer to any transportation infrastructure entity used for V2X communications. An RSU may be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, where an RSU implemented in or by a UE may be referred to as a “UE-type RSU,” an RSU implemented in or by an eNB may be referred to as an “eNB-type RSU,” an RSU implemented in or by a gNB may be referred to as a “gNB-type RSU,” and the like. In one example, an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs 101 (vUEs 101). The RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications/software to sense and control ongoing vehicular and pedestrian traffic. The RSU may operate on the 5.9 GHz Direct Short Range Communications (DSRC) band to provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may operate on the cellular V2X band to provide the aforementioned low latency communications, as well as other cellular communications services. Additionally or alternatively, the RSU may operate as a Wi-Fi hotspot (2.4 GHz band) and/or provide connectivity to one or more cellular networks to provide uplink and downlink communications. The computing device(s) and some or all of the radiofrequency circuitry of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller and/or a backhaul network.

Any of the RAN nodes 111 can terminate the air interface protocol and can be the first point of contact for the UEs 101. In some embodiments, any of the RAN nodes 111 can fulfill various logical functions for the RAN 110 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

In embodiments, the UEs 101 can be configured to communicate using OFDM communication signals with each other or with any of the RAN nodes 111 over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, an OFDMA communication technique (e.g., for downlink communications) or a SC-FDMA communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. The OFDM signals can include a plurality of orthogonal subcarriers.

In some embodiments, a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 111 to the UEs 101, while uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid, called a resource grid or time-frequency resource grid, which is the physical resource in the downlink in each slot. Such a time-frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation. Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to one slot in a radio frame. The smallest time-frequency unit in a resource grid is denoted as a resource element. Each resource grid includes a number of resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block includes a collection of resource elements; in the frequency domain, this may represent the smallest quantity of resources that currently can be allocated. There are several different physical downlink channels that are conveyed using such resource blocks.

According to various embodiments, the UEs 101 and the RAN nodes 111 communicate data (for example, transmit and receive) data over a licensed medium (also referred to as the “licensed spectrum” and/or the “licensed band”) and an unlicensed shared medium (also referred to as the “unlicensed spectrum” and/or the “unlicensed band”). The licensed spectrum may include channels that operate in the frequency range of approximately 400 MHz to approximately 3.8 GHz, whereas the unlicensed spectrum may include the 5 GHz band.

To operate in the unlicensed spectrum, the UEs 101 and the RAN nodes 111 may operate using LAA, eLAA, and/or feLAA mechanisms. In these implementations, the UEs 101 and the RAN nodes 111 may perform one or more known medium-sensing operations and/or carrier-sensing operations in order to determine whether one or more channels in the unlicensed spectrum is unavailable or otherwise occupied prior to transmitting in the unlicensed spectrum. The medium/carrier sensing operations may be performed according to a listen-before-talk (LBT) protocol.

LBT is a mechanism whereby equipment (for example, UEs 101 RAN nodes 111, etc.) senses a medium (for example, a channel or carrier frequency) and transmits when the medium is sensed to be idle (or when a specific channel in the medium is sensed to be unoccupied). The medium sensing operation may include CCA, which utilizes at least ED to determine the presence or absence of other signals on a channel in order to determine if a channel is occupied or clear. This LBT mechanism allows cellular/LAA networks to coexist with incumbent systems in the unlicensed spectrum and with other LAA networks. ED may include sensing RF energy across an intended transmission band for a period of time and comparing the sensed RF energy to a predefined or configured threshold.

Typically, the incumbent systems in the 5 GHz band are WLANs based on IEEE 802.11 technologies. WLAN employs a contention-based channel access mechanism, called CSMA/CA. Here, when a WLAN node (e.g., a mobile station (MS) such as UE 101, AP 106, or the like) intends to transmit, the WLAN node may first perform CCA before transmission. Additionally, a backoff mechanism is used to avoid collisions in situations where more than one WLAN node senses the channel as idle and transmits at the same time. The backoff mechanism may be a counter that is drawn randomly within the CWS, which is increased exponentially upon the occurrence of collision and reset to a minimum value when the transmission succeeds. The LBT mechanism designed for LAA is somewhat similar to the CSMA/CA of WLAN. In some implementations, the LBT procedure for DL or UL transmission bursts including PDSCH or PUSCH transmissions, respectively, may have an LAA contention window that is variable in length between X and Y ECCA slots, where X and Y are minimum and maximum values for the CWSs for LAA. In one example, the minimum CWS for an LAA transmission may be 9 microseconds (μs); however, the size of the CWS and a MCOT (for example, a transmission burst) may be based on governmental regulatory requirements.

The LAA mechanisms are built upon CA technologies of LTE-Advanced systems. In CA, each aggregated carrier is referred to as a CC. A CC may have a bandwidth of 1.4, 3, 5, 10, 15 or 20 MHz and a maximum of five CCs can be aggregated, and therefore, a maximum aggregated bandwidth is 100 MHz. In FDD systems, the number of aggregated carriers can be different for DL and UL, where the number of UL CCs is equal to or lower than the number of DL component carriers. In some cases, individual CCs can have a different bandwidth than other CCs. In TDD systems, the number of CCs as well as the bandwidths of each CC is usually the same for DL and UL.

CA also includes individual serving cells to provide individual CCs. The coverage of the serving cells may differ, for example, because CCs on different frequency bands will experience different pathloss. A primary service cell or PCell may provide a PCC for both UL and DL, and may handle RRC and NAS related activities. The other serving cells are referred to as SCells, and each SCell may provide an individual SCC for both UL and DL. The SCCs may be added and removed as required, while changing the PCC may require the UE 101 to undergo a handover. In LAA, eLAA, and feLAA, some or all of the SCells may operate in the unlicensed spectrum (referred to as “LAA SCells”), and the LAA SCells are assisted by a PCell operating in the licensed spectrum. When a UE is configured with more than one LAA SCell, the UE may receive UL grants on the configured LAA SCells indicating different PUSCH starting positions within a same subframe.

The PDSCH carries user data and higher-layer signaling to the UEs 101. The PDCCH carries information about the transport format and resource allocations related to the PDSCH channel, among other things. It may also inform the UEs 101 about the transport format, resource allocation, and HARQ information related to the uplink shared channel. Typically, downlink scheduling (assigning control and shared channel resource blocks to the UE 101 b within a cell) may be performed at any of the RAN nodes 111 based on channel quality information fed back from any of the UEs 101. The downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UEs 101.

The PDCCH uses CCEs to convey the control information. Before being mapped to resource elements, the PDCCH complex-valued symbols may first be organized into quadruplets, which may then be permuted using a sub-block interleaver for rate matching. Each PDCCH may be transmitted using one or more of these CCEs, where each CCE may correspond to nine sets of four physical resource elements known as REGs. Four Quadrature Phase Shift Keying (QPSK) symbols may be mapped to each REG. The PDCCH can be transmitted using one or more CCEs, depending on the size of the DCI and the channel condition. There can be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation level, L=1, 2, 4, or 8).

Some embodiments may use concepts for resource allocation for control channel information that are an extension of the above-described concepts. For example, some embodiments may utilize an EPDCCH that uses PDSCH resources for control information transmission. The EPDCCH may be transmitted using one or more ECCEs. Similar to above, each ECCE may correspond to nine sets of four physical resource elements known as EREGs. An ECCE may have other numbers of EREGs in some situations.

The RAN nodes 111 may be configured to communicate with one another via interface 112. In embodiments where the system 100 is an LTE system (e.g., when CN 120 is an EPC 220 as in FIG. 2), the interface 112 may be an X2 interface 112. The X2 interface may be defined between two or more RAN nodes 111 (e.g., two or more eNBs and the like) that connect to EPC 120, and/or between two eNBs connecting to EPC 120. In some implementations, the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). The X2-U may provide flow control mechanisms for user data packets transferred over the X2 interface, and may be used to communicate information about the delivery of user data between eNBs. For example, the X2-U may provide specific sequence number information for user data transferred from a MeNB to an SeNB; information about successful in sequence delivery of PDCP PDUs to a UE 101 from an SeNB for user data; information of PDCP PDUs that were not delivered to a UE 101; information about a current minimum desired buffer size at the SeNB for transmitting to the UE user data; and the like. The X2-C may provide intra-LTE access mobility functionality, including context transfers from source to target eNBs, user plane transport control, etc.; load management functionality; as well as inter-cell interference coordination functionality.

In embodiments where the system 100 is a 5G or NR system (e.g., when CN 120 is a 5GC 320 as in FIG. 3), the interface 112 may be an Xn interface 112. The Xn interface is defined between two or more RAN nodes 111 (e.g., two or more gNBs and the like) that connect to 5GC 120, between a RAN node 111 (e.g., a gNB) connecting to 5GC 120 and an eNB, and/or between two eNBs connecting to 5GC 120. In some implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. The Xn-U may provide non-guaranteed delivery of user plane PDUs and support/provide data forwarding and flow control functionality. The Xn-C may provide management and error handling functionality, functionality to manage the Xn-C interface; mobility support for UE 101 in a connected mode (e.g., CM-CONNECTED) including functionality to manage the UE mobility for connected mode between one or more RAN nodes 111. The mobility support may include context transfer from an old (source) serving RAN node 111 to new (target) serving RAN node 111, and control of user plane tunnels between old (source) serving RAN node 111 to new (target) serving RAN node 111. A protocol stack of the Xn-U may include a transport network layer built on Internet Protocol (IP) transport layer, and a GTP-U layer on top of a UDP and/or IP layer(s) to carry user plane PDUs. The Xn-C protocol stack may include an application layer signaling protocol (referred to as Xn Application Protocol (Xn-AP)) and a transport network layer that is built on SCTP. The SCTP may be on top of an IP layer, and may provide the guaranteed delivery of application layer messages. In the transport IP layer, point-to-point transmission is used to deliver the signaling PDUs. In other implementations, the Xn-U protocol stack and/or the Xn-C protocol stack may be same or similar to the user plane and/or control plane protocol stack(s) shown and described herein.

The RAN 110 is shown to be communicatively coupled to a core network-in this embodiment, core network (CN) 120. The CN 120 may include a plurality of network elements 122, which are configured to offer various data and telecommunications services to customers/subscribers (e.g., users of UEs 101) who are connected to the CN 120 via the RAN 110. The components of the CN 120 may be implemented in one physical node or separate physical nodes including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some embodiments, NFV may be utilized to virtualize any or all of the above-described network node functions via executable instructions stored in one or more computer-readable storage mediums (described in further detail below). A logical instantiation of the CN 120 may be referred to as a network slice, and a logical instantiation of a portion of the CN 120 may be referred to as a network sub-slice. NFV architectures and infrastructures may be used to virtualize one or more network functions, alternatively performed by proprietary hardware, onto physical resources including a combination of industry-standard server hardware, storage hardware, or switches. In other words, NFV systems can be used to execute virtual or reconfigurable implementations of one or more EPC components/functions.

Generally, the application server 130 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS PS domain, LTE PS data services, etc.). The application server 130 can also be configured to support one or more communication services (e.g., VoIP sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 101 via the EPC 120.

In embodiments, the CN 120 may be a 5GC (referred to as “5GC 120” or the like), and the RAN 110 may be connected with the CN 120 via an NG interface 113. In embodiments, the NG interface 113 may be split into two parts, an NG user plane (NG-U) interface 114, which carries traffic data between the RAN nodes 111 and a UPF, and the S1 control plane (NG-C) interface 115, which is a signaling interface between the RAN nodes 111 and AMFs. Embodiments where the CN 120 is a 5GC 120 are discussed in more detail with regard to FIG. 3.

In embodiments, the CN 120 may be a 5G CN (referred to as “5GC 120” or the like), while in other embodiments, the CN 120 may be an EPC). Where CN 120 is an EPC (referred to as “EPC 120” or the like), the RAN 110 may be connected with the CN 120 via an S1 interface 113. In embodiments, the S1 interface 113 may be split into two parts, an S1 user plane (S1-U) interface 114, which carries traffic data between the RAN nodes 111 and the S-GW, and the S1-MME interface 115, which is a signaling interface between the RAN nodes 111 and MMEs.

FIG. 2 illustrates an example architecture of a system 200 including a first CN 220, in accordance with various embodiments. In this example, system 200 may implement the LTE standard wherein the CN 220 is an EPC 220 that corresponds with CN 120 of FIG. 1. Additionally, the UE 201 may be the same or similar as the UEs 101 of FIG. 1, and the E-UTRAN 210 may be a RAN that is the same or similar to the RAN 110 of FIG. 1, and which may include RAN nodes 111 discussed previously. The CN 220 may include MMEs 221, an S-GW 222, a P-GW 223, a HSS 224, and a SGSN 225.

The MMEs 221 may be similar in function to the control plane of legacy SGSN, and may implement MM functions to keep track of the current location of a UE 201. The MMEs 221 may perform various MM procedures to manage mobility aspects in access such as gateway selection and tracking area list management. MM (also referred to as “EPS MM” or “EMM” in E-UTRAN systems) may refer to all applicable procedures, methods, data storage, etc. that are used to maintain knowledge about a present location of the UE 201, provide user identity confidentiality, and/or perform other like services to users/subscribers. Each UE 201 and the MME 221 may include an MM or EMM sublayer, and an MM context may be established in the UE 201 and the MME 221 when an attach procedure is successfully completed. The MM context may be a data structure or database object that stores MM-related information of the UE 201. The MMEs 221 may be coupled with the HSS 224 via an S6a reference point, coupled with the SGSN 225 via an S3 reference point, and coupled with the S-GW 222 via an S11 reference point.

The SGSN 225 may be a node that serves the UE 201 by tracking the location of an individual UE 201 and performing security functions. In addition, the SGSN 225 may perform Inter-EPC node signaling for mobility between 2G/3G and E-UTRAN 3GPP access networks; PDN and S-GW selection as specified by the MMEs 221; handling of UE 201 time zone functions as specified by the MMEs 221; and MME selection for handovers to E-UTRAN 3GPP access network. The S3 reference point between the MMEs 221 and the SGSN 225 may enable user and bearer information exchange for inter-3GPP access network mobility in idle and/or active states.

The HSS 224 may include a database for network users, including subscription-related information to support the network entities' handling of communication sessions. The EPC 220 may include one or several HSSs 224, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc. For example, the HSS 224 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc. An S6a reference point between the HSS 224 and the MMEs 221 may enable transfer of subscription and authentication data for authenticating/authorizing user access to the EPC 220 between HSS 224 and the MMEs 221.

The S-GW 222 may terminate the S1 interface 113 (“S1-U” in FIG. 2) toward the RAN 210, and routes data packets between the RAN 210 and the EPC 220. In addition, the S-GW 222 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement. The S11 reference point between the S-GW 222 and the MMEs 221 may provide a control plane between the MMEs 221 and the S-GW 222. The S-GW 222 may be coupled with the P-GW 223 via an S5 reference point.

The P-GW 223 may terminate an SGi interface toward a PDN 230. The P-GW 223 may route data packets between the EPC 220 and external networks such as a network including the application server 130 (alternatively referred to as an “AF”) via an IP interface 125 (see e.g., FIG. 1). In embodiments, the P-GW 223 may be communicatively coupled to an application server (application server 130 of FIG. 1 or PDN 230 in FIG. 2) via an IP communications interface 125 (see, e.g., FIG. 1). The S5 reference point between the P-GW 223 and the S-GW 222 may provide user plane tunneling and tunnel management between the P-GW 223 and the S-GW 222. The S5 reference point may also be used for S-GW 222 relocation due to UE 201 mobility and if the S-GW 222 needs to connect to a non-collocated P-GW 223 for the required PDN connectivity. The P-GW 223 may further include a node for policy enforcement and charging data collection (e.g., PCEF (not shown)). Additionally, the SGi reference point between the P-GW 223 and the packet data network (PDN) 230 may be an operator external public, a private PDN, or an intra operator packet data network, for example, for provision of IMS services. The P-GW 223 may be coupled with a PCRF 226 via a Gx reference point.

PCRF 226 is the policy and charging control element of the EPC 220. In a non-roaming scenario, there may be a single PCRF 226 in the Home Public Land Mobile Network (HPLMN) associated with a UE 20 l's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with local breakout of traffic, there may be two PCRFs associated with a UE 201's IP-CAN session, a Home PCRF (H-PCRF) within an HPLMN and a Visited PCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF 226 may be communicatively coupled to the application server 230 via the P-GW 223. The application server 230 may signal the PCRF 226 to indicate a new service flow and select the appropriate QoS and charging parameters. The PCRF 226 may provision this rule into a PCEF (not shown) with the appropriate TFT and QCI, which commences the QoS and charging as specified by the application server 230. The Gx reference point between the PCRF 226 and the P-GW 223 may allow for the transfer of QoS policy and charging rules from the PCRF 226 to PCEF in the P-GW 223. An Rx reference point may reside between the PDN 230 (or “AF 230”) and the PCRF 226.

FIG. 3 illustrates an architecture of a system 300 including a second CN 320 in accordance with various embodiments. The system 300 is shown to include a UE 301, which may be the same or similar to the UEs 101 and UE 201 discussed previously; a (R)AN 310, which may be the same or similar to the RAN 110 and RAN 210 discussed previously, and which may include RAN nodes 111 discussed previously; and a DN 303, which may be, for example, operator services, Internet access or 3rd party services; and a 5GC 320. The 5GC 320 may include an AUSF 322; an AMF 321; a SMF 324; a NEF 323. a PCF 326; a NRF 325; a UDM 327; an AF 328; a UPF 302; and a NSSF 329.

The UPF 302 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to DN 303, and a branching point to support multi-homed PDU session. The UPF 302 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS handling for a user plane (e.g., packet filtering, gating, UL/DL rate enforcement), perform Uplink Traffic verification (e.g., SDF to QoS flow mapping), transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. UPF 302 may include an uplink classifier to support routing traffic flows to a data network. The DN 303 may represent various network operator services, Internet access, or third party services. DN 303 may include, or be similar to, application server 130 discussed previously. The UPF 302 may interact with the SMF 324 via an N4 reference point between the SMF 324 and the UPF 302.

The AUSF 322 may store data for authentication of UE 301 and handle authentication-related functionality. The AUSF 322 may facilitate a common authentication framework for various access types. The AUSF 322 may communicate with the AMF 321 via an N12 reference point between the AMF 321 and the AUSF 322; and may communicate with the UDM 327 via an N13 reference point between the UDM 327 and the AUSF 322. Additionally, the AUSF 322 may exhibit an Nausf service-based interface.

The AMF 321 may be responsible for registration management (e.g., for registering UE 301, etc.), connection management, reachability management, mobility management, and lawful interception of AMF-related events, and access authentication and authorization. The AMF 321 may be a termination point for the an N11 reference point between the AMF 321 and the SMF 324. The AMF 321 may provide transport for SM messages between the UE 301 and the SMF 324, and act as a transparent proxy for routing SM messages. AMF 321 may also provide transport for SMS messages between UE 301 and an SMSF (not shown by FIG. 3). AMF 321 may act as SEAF, which may include interaction with the AUSF 322 and the UE 301, receipt of an intermediate key that was established as a result of the UE 301 authentication process. Where USIM based authentication is used, the AMF 321 may retrieve the security material from the AUSF 322. AMF 321 may also include a SCM function, which receives a key from the SEA that it uses to derive access-network specific keys. Furthermore, AMF 321 may be a termination point of a RAN CP interface, which may include or be an N2 reference point between the (R)AN 310 and the AMF 321; and the AMF 321 may be a termination point of NAS (N1) signalling, and perform NAS ciphering and integrity protection.

AMF 321 may also support NAS signalling with a UE 301 over an Non-3GPP Interworking Function (N3IWF) interface. The N3IWF may be used to provide access to untrusted entities. N3IWF may be a termination point for the N2 interface between the (R)AN 310 and the AMF 321 for the control plane, and may be a termination point for the N3 reference point between the (R)AN 310 and the UPF 302 for the user plane. As such, the AMF 321 may handle N2 signalling from the SMF 324 and the AMF 321 for PDU sessions and QoS, encapsulate/de-encapsulate packets for IPSec and N3 tunneling, mark N3 user-plane packets in the uplink, and enforce QoS corresponding to N3 packet marking taking into account QoS requirements associated with such marking received over N2. N3IWF may also relay uplink and downlink control-plane NAS signalling between the UE 301 and AMF 321 via an N1 reference point between the UE 301 and the AMF 321, and relay uplink and downlink user-plane packets between the UE 301 and UPF 302. The N3IWF also provides mechanisms for IPsec tunnel establishment with the UE 301. The AMF 321 may exhibit an Namf service-based interface, and may be a termination point for an N14 reference point between two AMFs 321 and an N17 reference point between the AMF 321 and a 5G-EIR (not shown by FIG. 3).

The UE 301 may need to register with the AMF 321 in order to receive network services. RM is used to register or deregister the UE 301 with the network (e.g., AMF 321), and establish a UE context in the network (e.g., AMF 321). The UE 301 may operate in an RM-REGISTERED state or an RM-DEREGISTERED state. In the RM-DEREGISTERED state, the UE 301 is not registered with the network, and the UE context in AMF 321 holds no valid location or routing information for the UE 301 so the UE 301 is not reachable by the AMF 321. In the RM-REGISTERED state, the UE 301 is registered with the network, and the UE context in AMF 321 may hold a valid location or routing information for the UE 301 so the UE 301 is reachable by the AMF 321. In the RM-REGISTERED state, the UE 301 may perform mobility Registration Update procedures, perform periodic Registration Update procedures triggered by expiration of the periodic update timer (e.g., to notify the network that the UE 301 is still active), and perform a Registration Update procedure to update UE capability information or to re-negotiate protocol parameters with the network, among others.

The AMF 321 may store one or more RM contexts for the UE 301, where each RM context is associated with a specific access to the network. The RM context may be a data structure, database object, etc. that indicates or stores, inter alia, a registration state per access type and the periodic update timer. The AMF 321 may also store a 5GC MM context that may be the same or similar to the (E)MM context discussed previously. In various embodiments, the AMF 321 may store a CE mode B Restriction parameter of the UE 301 in an associated MM context or RM context. The AMF 321 may also derive the value, when needed, from the UE's usage setting parameter already stored in the UE context (and/or MM/RM context).

CM may be used to establish and release a signaling connection between the UE 301 and the AMF 321 over the N1 interface. The signaling connection is used to enable NAS signaling exchange between the UE 301 and the CN 320, and includes both the signaling connection between the UE and the AN (e.g., RRC connection or UE-N3IWF connection for non-3GPP access) and the N2 connection for the UE 301 between the AN (e.g., RAN 310) and the AMF 321. The UE 301 may operate in one of two CM states, CM-IDLE mode or CM-CONNECTED mode. When the UE 301 is operating in the CM-IDLE state/mode, the UE 301 may have no NAS signaling connection established with the AMF 321 over the N1 interface, and there may be (R)AN 310 signaling connection (e.g., N2 and/or N3 connections) for the UE 301. When the UE 301 is operating in the CM-CONNECTED state/mode, the UE 301 may have an established NAS signaling connection with the AMF 321 over the N1 interface, and there may be a (R)AN 310 signaling connection (e.g., N2 and/or N3 connections) for the UE 301. Establishment of an N2 connection between the (R)AN 310 and the AMF 321 may cause the UE 301 to transition from CM-IDLE mode to CM-CONNECTED mode, and the UE 301 may transition from the CM-CONNECTED mode to the CM-IDLE mode when N2 signaling between the (R)AN 310 and the AMF 321 is released.

The SMF 324 may be responsible for SM (e.g., session establishment, modify and release, including tunnel maintain between UPF and AN node); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement and QoS; lawful intercept (for SM events and interface to LI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF over N2 to AN; and determining SSC mode of a session. SM may refer to management of a PDU session, and a PDU session or “session” may refer to a PDU connectivity service that provides or enables the exchange of PDUs between a UE 301 and a data network (DN) 303 identified by a Data Network Name (DNN). PDU sessions may be established upon UE 301 request, modified upon UE 301 and 5GC 320 request, and released upon UE 301 and 5GC 320 request using NAS SM signaling exchanged over the N1 reference point between the UE 301 and the SMF 324. Upon request from an application server, the 5GC 320 may trigger a specific application in the UE 301. In response to receipt of the trigger message, the UE 301 may pass the trigger message (or relevant parts/information of the trigger message) to one or more identified applications in the UE 301. The identified application(s) in the UE 301 may establish a PDU session to a specific DNN. The SMF 324 may check whether the UE 301 requests are compliant with user subscription information associated with the UE 301. In this regard, the SMF 324 may retrieve and/or request to receive update notifications on SMF 324 level subscription data from the UDM 327.

The SMF 324 may include the following roaming functionality: handling local enforcement to apply QoS SLAs (VPLMN); charging data collection and charging interface (VPLMN); lawful intercept (in VPLMN for SM events and interface to LI system); and support for interaction with external DN for transport of signalling for PDU session authorization/authentication by external DN. An N16 reference point between two SMFs 324 may be included in the system 300, which may be between another SMF 324 in a visited network and the SMF 324 in the home network in roaming scenarios. Additionally, the SMF 324 may exhibit the Nsmf service-based interface.

The NEF 323 may provide means for securely exposing the services and capabilities provided by 3GPP network functions for third party, internal exposure/re-exposure, Application Functions (e.g., AF 328), edge computing or fog computing systems, etc. In such embodiments, the NEF 323 may authenticate, authorize, and/or throttle the AFs. NEF 323 may also translate information exchanged with the AF 328 and information exchanged with internal network functions. For example, the NEF 323 may translate between an AF-Service-Identifier and an internal 5GC information. NEF 323 may also receive information from other network functions (NFs) based on exposed capabilities of other network functions. This information may be stored at the NEF 323 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 323 to other NFs and AFs, and/or used for other purposes such as analytics. Additionally, the NEF 323 may exhibit an Nnef service-based interface.

The NRF 325 may support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 325 also maintains information of available NF instances and their supported services. As used herein, the terms “instantiate,” “instantiation,” and the like may refer to the creation of an instance, and an “instance” may refer to a concrete occurrence of an object, which may occur, for example, during execution of program code. Additionally, the NRF 325 may exhibit the Nnrf service-based interface.

The PCF 326 may provide policy rules to control plane function(s) to enforce them, and may also support unified policy framework to govern network behaviour. The PCF 326 may also implement an FE to access subscription information relevant for policy decisions in a UDR of the UDM 327. The PCF 326 may communicate with the AMF 321 via an N15 reference point between the PCF 326 and the AMF 321, which may include a PCF 326 in a visited network and the AMF 321 in case of roaming scenarios. The PCF 326 may communicate with the AF 328 via an N5 reference point between the PCF 326 and the AF 328; and with the SMF 324 via an N7 reference point between the PCF 326 and the SMF 324. The system 300 and/or CN 320 may also include an N24 reference point between the PCF 326 (in the home network) and a PCF 326 in a visited network. Additionally, the PCF 326 may exhibit an Npcf service-based interface.

The UDM 327 may handle subscription-related information to support the network entities' handling of communication sessions, and may store subscription data of UE 301. For example, subscription data may be communicated between the UDM 327 and the AMF 321 via an N8 reference point between the UDM 327 and the AMF. The UDM 327 may include two parts, an application FE and a UDR (the FE and UDR are not shown by FIG. 3). The UDR may store subscription data and policy data for the UDM 327 and the PCF 326, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 301) for the NEF 323. The Nudr service-based interface may be exhibited by the UDR 221 to allow the UDM 327, PCF 326, and NEF 323 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR. The UDM may include a UDM-FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration/mobility management, and subscription management. The UDR may interact with the SMF 324 via an N10 reference point between the UDM 327 and the SMF 324. UDM 327 may also support SMS management, wherein an SMS-FE implements the similar application logic as discussed previously. Additionally, the UDM 327 may exhibit the Nudm service-based interface.

The AF 328 may provide application influence on traffic routing, provide access to the NCE, and interact with the policy framework for policy control. The NCE may be a mechanism that allows the 5GC 320 and AF 328 to provide information to each other via NEF 323, which may be used for edge computing implementations. In such implementations, the network operator and third party services may be hosted close to the UE 301 access point of attachment to achieve an efficient service delivery through the reduced end-to-end latency and load on the transport network. For edge computing implementations, the 5GC may select a UPF 302 close to the UE 301 and execute traffic steering from the UPF 302 to DN 303 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 328. In this way, the AF 328 may influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 328 is considered to be a trusted entity, the network operator may permit AF 328 to interact directly with relevant NFs. Additionally, the AF 328 may exhibit an Naf service-based interface.

The NSSF 329 may select a set of network slice instances serving the UE 301. The NSSF 329 may also determine allowed NSSAI and the mapping to the subscribed S-NSSAIs, if needed. The NSSF 329 may also determine the AMF set to be used to serve the UE 301, or a list of candidate AMF(s) 321 based on a suitable configuration and possibly by querying the NRF 325. The selection of a set of network slice instances for the UE 301 may be triggered by the AMF 321 with which the UE 301 is registered by interacting with the NSSF 329, which may lead to a change of AMF 321. The NSSF 329 may interact with the AMF 321 via an N22 reference point between AMF 321 and NSSF 329; and may communicate with another NSSF 329 in a visited network via an N31 reference point (not shown by FIG. 3). Additionally, the NSSF 329 may exhibit an Nnssf service-based interface.

As discussed previously, the CN 320 may include an SMSF, which may be responsible for SMS subscription checking and verification, and relaying SM messages to/from the UE 301 to/from other entities, such as an SMS-GMSC/IWMSC/SMS-router. The SMS may also interact with AMF 321 and UDM 327 for a notification procedure that the UE 301 is available for SMS transfer (e.g., set a UE not reachable flag, and notifying UDM 327 when UE 301 is available for SMS).

The CN 120 may also include other elements that are not shown by FIG. 3, such as a Data Storage system/architecture, a 5G-EIR, a SEPP, and the like. The Data Storage system may include a SDSF, an UDSF, and/or the like. Any NF may store and retrieve unstructured data into/from the UDSF (e.g., UE contexts), via N18 reference point between any NF and the UDSF (not shown by FIG. 3). Individual NFs may share a UDSF for storing their respective unstructured data or individual NFs may each have their own UDSF located at or near the individual NFs. Additionally, the UDSF may exhibit a Nudsf service-based interface (not shown by FIG. 3). The 5G-EIR may be an NF that checks the status of PEI for determining whether particular equipment/entities are blacklisted from the network; and the SEPP may be a non-transparent proxy that performs topology hiding, message filtering, and policing on inter-PLMN control plane interfaces.

Additionally, there may be many more reference points and/or service-based interfaces between the NF services in the NFs; however, these interfaces and reference points have been omitted from FIG. 3 for clarity. In one example, the CN 320 may include an Nx interface, which is an inter-CN interface between the MME (e.g., MME 221) and the AMF 321 in order to enable interworking between CN 320 and CN 220. Other example interfaces/reference points may include an N5g-EIR service-based interface exhibited by a 5G-EIR, an N27 reference point between the NRF in the visited network and the NRF in the home network; and an N31 reference point between the NSSF in the visited network and the NSSF in the home network.

FIG. 4 illustrates an example of infrastructure equipment 400 in accordance with various embodiments. The infrastructure equipment 400 (or “system 400”) may be implemented as a base station, radio head, RAN node such as the RAN nodes 111 and/or AP 106 shown and described previously, application server(s) 130, and/or any other element/device discussed herein. In other examples, the system 400 could be implemented in or by a UE.

The system 400 includes application circuitry 405, baseband circuitry 410, one or more radio front end modules (RFEMs) 415, memory circuitry 420, power management integrated circuitry (PMIC) 425, power tee circuitry 430, network controller circuitry 435, network interface connector 440, satellite positioning circuitry 445, and user interface 450. In some embodiments, the device 400 may include additional elements such as, for example, memory/storage, display, camera, sensor, or input/output (I/O) interface. In other embodiments, the components described below may be included in more than one device. For example, said circuitries may be separately included in more than one device for CRAN, vBBU, or other like implementations.

Application circuitry 405 includes circuitry such as, but not limited to one or more processors (or processor cores), cache memory, and one or more of low drop-out voltage regulators (LDOs), interrupt controllers, serial interfaces such as SPI, I2C or universal programmable serial interface module, real time clock (RTC), timer-counters including interval and watchdog timers, general purpose input/output (I/O or IO), memory card controllers such as Secure Digital (SD) MultiMediaCard (MMC) or similar, Universal Serial Bus (USB) interfaces, Mobile Industry Processor Interface (MIPI) interfaces and Joint Test Access Group (JTAG) test access ports. The processors (or cores) of the application circuitry 405 may be coupled with or may include memory/storage elements and may be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the system 400. In some implementations, the memory/storage elements may be on-chip memory circuitry, which may include any suitable volatile and/or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, Flash memory, solid-state memory, and/or any other type of memory device technology, such as those discussed herein.

The processor(s) of application circuitry 405 may include, for example, one or more processor cores (CPUs), one or more application processors, one or more graphics processing units (GPUs), one or more reduced instruction set computing (RISC) processors, one or more Acorn RISC Machine (ARM) processors, one or more complex instruction set computing (CISC) processors, one or more digital signal processors (DSP), one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, or any suitable combination thereof. In some embodiments, the application circuitry 405 may include, or may be, a special-purpose processor/controller to operate according to the various embodiments herein. As examples, the processor(s) of application circuitry 405 may include one or more Intel Pentium®, Core®, or Xeon® processor(s); Advanced Micro Devices (AMD) Ryzen® processor(s), Accelerated Processing Units (APUs), or Epyc® processors; ARM-based processor(s) licensed from ARM Holdings, Ltd. such as the ARM Cortex-A family of processors and the ThunderX2® provided by Cavium™, Inc.; a MIPS-based design from MIPS Technologies, Inc. such as MIPS Warrior P-class processors; and/or the like. In some embodiments, the system 400 may not utilize application circuitry 405, and instead may include a special-purpose processor/controller to process IP data received from an EPC or 5GC, for example.

In some implementations, the application circuitry 405 may include one or more hardware accelerators, which may be microprocessors, programmable processing devices, or the like. The one or more hardware accelerators may include, for example, computer vision (CV) and/or deep learning (DL) accelerators. As examples, the programmable processing devices may be one or more a field-programmable devices (FPDs) such as field-programmable gate arrays (FPGAs) and the like; programmable logic devices (PLDs) such as complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), and the like; ASICs such as structured ASICs and the like; programmable SoCs (PSoCs); and the like. In such implementations, the circuitry of application circuitry 405 may include logic blocks or logic fabric, and other interconnected resources that may be programmed to perform various functions, such as the procedures, methods, functions, etc. of the various embodiments discussed herein. In such embodiments, the circuitry of application circuitry 405 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), anti-fuses, etc.)) used to store logic blocks, logic fabric, data, etc. in look-up-tables (LUTs) and the like.

The baseband circuitry 410 may be implemented, for example, as a solder-down substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board or a multi-chip module containing two or more integrated circuits. The various hardware electronic elements of baseband circuitry 410 are discussed infra with regard to FIG. 6.

User interface circuitry 450 may include one or more user interfaces designed to enable user interaction with the system 400 or peripheral component interfaces designed to enable peripheral component interaction with the system 400. User interfaces may include, but are not limited to, one or more physical or virtual buttons (e.g., a reset button), one or more indicators (e.g., light emitting diodes (LEDs)), a physical keyboard or keypad, a mouse, a touchpad, a touchscreen, speakers or other audio emitting devices, microphones, a printer, a scanner, a headset, a display screen or display device, etc. Peripheral component interfaces may include, but are not limited to, a nonvolatile memory port, a universal serial bus (USB) port, an audio jack, a power supply interface, etc.

The radio front end modules (RFEMs) 415 may include a millimeter wave (mmWave) RFEM and one or more sub-mmWave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-mmWave RFICs may be physically separated from the mmWave RFEM. The RFICs may include connections to one or more antennas or antenna arrays (see e.g., antenna array 611 of FIG. 6 infra), and the RFEM may be connected to multiple antennas. In alternative implementations, both mmWave and sub-mmWave radio functions may be implemented in the same physical RFEM 415, which incorporates both mmWave antennas and sub-mmWave.

The memory circuitry 420 may include one or more of volatile memory including dynamic random access memory (DRAM) and/or synchronous dynamic random access memory (SDRAM), and nonvolatile memory (NVM) including high-speed electrically erasable memory (commonly referred to as Flash memory), phase change random access memory (PRAM), magnetoresistive random access memory (MRAM), etc., and may incorporate the three-dimensional (3D) cross-point (XPOINT) memories from Intel® and Micron®. Memory circuitry 420 may be implemented as one or more of solder down packaged integrated circuits, socketed memory modules and plug-in memory cards.

The PMIC 425 may include voltage regulators, surge protectors, power alarm detection circuitry, and one or more backup power sources such as a battery or capacitor. The power alarm detection circuitry may detect one or more of brown out (under-voltage) and surge (over-voltage) conditions. The power tee circuitry 430 may provide for electrical power drawn from a network cable to provide both power supply and data connectivity to the infrastructure equipment 400 using a single cable.

The network controller circuitry 435 may provide connectivity to a network using a standard network interface protocol such as Ethernet, Ethernet over GRE Tunnels, Ethernet over Multiprotocol Label Switching (MPLS), or some other suitable protocol. Network connectivity may be provided to/from the infrastructure equipment 400 via network interface connector 440 using a physical connection, which may be electrical (commonly referred to as a “copper interconnect”), optical, or wireless. The network controller circuitry 435 may include one or more dedicated processors and/or FPGAs to communicate using one or more of the aforementioned protocols. In some implementations, the network controller circuitry 435 may include multiple controllers to provide connectivity to other networks using the same or different protocols.

The positioning circuitry 445 includes circuitry to receive and decode signals transmitted/broadcasted by a positioning network of a global navigation satellite system (GNSS). Examples of navigation satellite constellations (or GNSS) include United States' Global Positioning System (GPS), Russia's Global Navigation System (GLONASS), the European Union's Galileo system, China's BeiDou Navigation Satellite System, a regional navigation system or GNSS augmentation system (e.g., Navigation with Indian Constellation (NAVIC), Japan's Quasi-Zenith Satellite System (QZSS), France's Doppler Orbitography and Radio-positioning Integrated by Satellite (DORIS), etc.), or the like. The positioning circuitry 445 includes various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, and the like to facilitate OTA communications) to communicate with components of a positioning network, such as navigation satellite constellation nodes. In some embodiments, the positioning circuitry 445 may include a Micro-Technology for Positioning, Navigation, and Timing (Micro-PNT) IC that uses a master timing clock to perform position tracking/estimation without GNSS assistance. The positioning circuitry 445 may also be part of, or interact with, the baseband circuitry 410 and/or RFEMs 415 to communicate with the nodes and components of the positioning network. The positioning circuitry 445 may also provide position data and/or time data to the application circuitry 405, which may use the data to synchronize operations with various infrastructure (e.g., RAN nodes 111, etc.), or the like.

The components shown by FIG. 4 may communicate with one another using interface circuitry, which may include any number of bus and/or interconnect (IX) technologies such as industry standard architecture (ISA), extended ISA (EISA), peripheral component interconnect (PCI), peripheral component interconnect extended (PCIx), PCI express (PCIe), or any number of other technologies. The bus/IX may be a proprietary bus, for example, used in a SoC based system. Other bus/IX systems may be included, such as an 12C interface, an SPI interface, point to point interfaces, and a power bus, among others.

FIG. 5 illustrates an example of a platform 500 (or “device 500”) in accordance with various embodiments. In embodiments, the computer platform 500 may be suitable for use as UEs 101, 201, 301, application servers 130, and/or any other element/device discussed in this document. The platform 500 may include any combinations of the components shown in the example. The components of platform 500 may be implemented as integrated circuits (ICs), portions thereof, discrete electronic devices, or other modules, logic, hardware, software, firmware, or a combination thereof adapted in the computer platform 500, or as components otherwise incorporated within a chassis of a larger system. The block diagram of FIG. 5 is intended to show a high level view of components of the computer platform 500. However, some of the components shown may be omitted, additional components may be present, and different arrangement of the components shown may occur in other implementations.

Application circuitry 505 includes circuitry such as, but not limited to one or more processors (or processor cores), cache memory, and one or more of LDOs, interrupt controllers, serial interfaces such as SPI, 12C or universal programmable serial interface module, RTC, timer-counters including interval and watchdog timers, general purpose I/O, memory card controllers such as SD MMC or similar, USB interfaces, MIPI interfaces, and JTAG test access ports. The processors (or cores) of the application circuitry 505 may be coupled with or may include memory/storage elements and may be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the system 500. In some implementations, the memory/storage elements may be on-chip memory circuitry, which may include any suitable volatile and/or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, Flash memory, solid-state memory, and/or any other type of memory device technology, such as those discussed in this document.

The processor(s) of application circuitry 405 may include, for example, one or more processor cores, one or more application processors, one or more GPUs, one or more RISC processors, one or more ARM processors, one or more CISC processors, one or more DSP, one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, a multithreaded processor, an ultra-low voltage processor, an embedded processor, some other known processing element, or any suitable combination thereof. In some embodiments, the application circuitry 405 may include, or may be, a special-purpose processor/controller to operate according to the various embodiments in this document.

As examples, the processor(s) of application circuitry 505 may include an Intel® Architecture Core™ based processor, such as a Quarkrm, an Atom™, an i3, an i5, an i7, or an MCU-class processor, or another such processor available from Intel® Corporation, Santa Clara, Calif. The processors of the application circuitry 505 may also be one or more of Advanced Micro Devices (AMD) Ryzen® processor(s) or Accelerated Processing Units (APUs); A5-A9 processor(s) from Apple® Inc., Snapdragon™ processor(s) from Qualcomm® Technologies, Inc., Texas Instruments, Inc.® Open Multimedia Applications Platform (OMAP)™ processor(s); a MIPS-based design from MIPS Technologies, Inc. such as MIPS Warrior M-class, Warrior I-class, and Warrior P-class processors; an ARM-based design licensed from ARM Holdings, Ltd., such as the ARM Cortex-A, Cortex-R, and Cortex-M family of processors; or the like. In some implementations, the application circuitry 505 may be a part of a system on a chip (SoC) in which the application circuitry 505 and other components are formed into a single integrated circuit, or a single package, such as the Edison™ or Galileo™ SoC boards from Intel® Corporation.

Additionally or alternatively, application circuitry 505 may include circuitry such as, but not limited to, one or more a field-programmable devices (FPDs) such as FPGAs and the like; programmable logic devices (PLDs) such as complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), and the like; ASICs such as structured ASICs and the like; programmable SoCs (PSoCs); and the like. In such embodiments, the circuitry of application circuitry 505 may include logic blocks or logic fabric, and other interconnected resources that may be programmed to perform various functions, such as the procedures, methods, functions, etc. of the various embodiments discussed in this document. In such embodiments, the circuitry of application circuitry 505 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), anti-fuses, etc.)) used to store logic blocks, logic fabric, data, etc. in look-up tables (LUTs) and the like.

The baseband circuitry 510 may be implemented, for example, as a solder-down substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board or a multi-chip module containing two or more integrated circuits. The various hardware electronic elements of baseband circuitry 510 are discussed infra with regard to FIG. 6.

The RFEMs 515 may include a millimeter wave (mmWave) RFEM and one or more sub-mmWave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-mmWave RFICs may be physically separated from the mmWave RFEM. The RFICs may include connections to one or more antennas or antenna arrays (see e.g., antenna array 611 of FIG. 6 infra), and the RFEM may be connected to multiple antennas. In alternative implementations, both mmWave and sub-mmWave radio functions may be implemented in the same physical RFEM 515, which incorporates both mmWave antennas and sub-mmWave.

The memory circuitry 520 may include any number and type of memory devices used to provide for a given amount of system memory. As examples, the memory circuitry 520 may include one or more of volatile memory including random access memory (RAM), dynamic RAM (DRAM) and/or synchronous dynamic RAM (SDRAM), and nonvolatile memory (NVM) including high-speed electrically erasable memory (commonly referred to as Flash memory), phase change random access memory (PRAM), magnetoresistive random access memory (MRAM), etc. The memory circuitry 520 may be developed in accordance with a Joint Electron Devices Engineering Council (JEDEC) low power double data rate (LPDDR)-based design, such as LPDDR2, LPDDR3, LPDDR4, or the like. Memory circuitry 520 may be implemented as one or more of solder down packaged integrated circuits, single die package (SDP), dual die package (DDP) or quad die package (Q17P), socketed memory modules, dual inline memory modules (DIMMs) including microDIMMs or MiniDIMMs, and/or soldered onto a motherboard via a ball grid array (BGA). In low power implementations, the memory circuitry 520 may be on-die memory or registers associated with the application circuitry 505. To provide for persistent storage of information such as data, applications, operating systems and so forth, memory circuitry 520 may include one or more mass storage devices, which may include, inter alia, a solid state disk drive (SSDD), hard disk drive (HDD), a micro HDD, resistance change memories, phase change memories, holographic memories, or chemical memories, among others. For example, the computer platform 500 may incorporate the three-dimensional (3D) cross-point (XPOINT) memories from Intel® and Micron®.

Removable memory circuitry 523 may include devices, circuitry, enclosures/housings, ports or receptacles, etc. used to couple portable data storage devices with the platform 500. These portable data storage devices may be used for mass storage purposes, and may include, for example, flash memory cards (e.g., Secure Digital (SD) cards, microSD cards, xD picture cards, and the like), and USB flash drives, optical discs, external HDDs, and the like.

The platform 500 may also include interface circuitry (not shown) that is used to connect external devices with the platform 500. The external devices connected to the platform 500 via the interface circuitry include sensor circuitry 521 and electro-mechanical components (EMCs) 522, as well as removable memory devices coupled to removable memory circuitry 523.

The sensor circuitry 521 include devices, modules, or subsystems whose purpose is to detect events or changes in its environment and send the information (sensor data) about the detected events to some other a device, module, subsystem, etc. Examples of such sensors include, inter alia, inertia measurement units (IMUs) including accelerometers, gyroscopes, and/or magnetometers; microelectromechanical systems (MEMS) or nanoelectromechanical systems (NEMS) including 3-axis accelerometers, 3-axis gyroscopes, and/or magnetometers; level sensors; flow sensors; temperature sensors (e.g., thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (e.g., cameras or lensless apertures); light detection and ranging (LiDAR) sensors; proximity sensors (e.g., infrared radiation detector and the like), depth sensors, ambient light sensors, ultrasonic transceivers; microphones or other like audio capture devices; etc.

EMCs 522 include devices, modules, or subsystems whose purpose is to enable platform 500 to change its state, position, and/or orientation, or move or control a mechanism or (sub)system. Additionally, EMCs 522 may be configured to generate and send messages/signaling to other components of the platform 500 to indicate a current state of the EMCs 522. Examples of the EMCs 522 include one or more power switches, relays including electromechanical relays (EMRs) and/or solid state relays (SSRs), actuators (e.g., valve actuators, etc.), an audible sound generator, a visual warning device, motors (e.g., DC motors, stepper motors, etc.), wheels, thrusters, propellers, claws, clamps, hooks, and/or other like electro-mechanical components. In embodiments, platform 500 is configured to operate one or more EMCs 522 based on one or more captured events and/or instructions or control signals received from a service provider and/or various clients.

In some implementations, the interface circuitry may connect the platform 500 with positioning circuitry 545. The positioning circuitry 545 includes circuitry to receive and decode signals transmitted/broadcasted by a positioning network of a GNSS. Examples of navigation satellite constellations (or GNSS) include United States' GPS, Russia's GLONASS, the European Union's Galileo system, China's BeiDou Navigation Satellite System, a regional navigation system or GNSS augmentation system (e.g., NAVIC), Japan's QZSS, France's DORIS, etc.), or the like. The positioning circuitry 545 includes various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, and the like to facilitate OTA communications) to communicate with components of a positioning network, such as navigation satellite constellation nodes. In some embodiments, the positioning circuitry 545 may include a Micro-PNT IC that uses a master timing clock to perform position tracking/estimation without GNSS assistance. The positioning circuitry 545 may also be part of, or interact with, the baseband circuitry 410 and/or RFEMs 515 to communicate with the nodes and components of the positioning network. The positioning circuitry 545 may also provide position data and/or time data to the application circuitry 505, which may use the data to synchronize operations with various infrastructure (e.g., radio base stations), for turn-by-turn navigation applications, or the like

In some implementations, the interface circuitry may connect the platform 500 with Near-Field Communication (NFC) circuitry 540. NFC circuitry 540 is configured to provide contactless, short-range communications based on radio frequency identification (RFID) standards, wherein magnetic field induction is used to enable communication between NFC circuitry 540 and NFC-enabled devices external to the platform 500 (e.g., an “NFC touchpoint”). NFC circuitry 540 includes an NFC controller coupled with an antenna element and a processor coupled with the NFC controller. The NFC controller may be a chip/IC providing NFC functionalities to the NFC circuitry 540 by executing NFC controller firmware and an NFC stack. The NFC stack may be executed by the processor to control the NFC controller, and the NFC controller firmware may be executed by the NFC controller to control the antenna element to emit short-range RF signals. The RF signals may power a passive NFC tag (e.g., a microchip embedded in a sticker or wristband) to transmit stored data to the NFC circuitry 540, or initiate data transfer between the NFC circuitry 540 and another active NFC device (e.g., a smartphone or an NFC-enabled POS terminal) that is proximate to the platform 500.

In some implementations, the interface circuitry may connect the platform 500 with communications circuitry 560. Though communications circuitry 560 is shown as separate from the RFEM 515, these modules can form a single, combined module. The communication circuitry 560 is configured to enable the platform 500 to communicate on the cellular network, as subsequently described in relation to FIG. 7.

The driver circuitry 546 may include software and hardware elements that operate to control particular devices that are embedded in the platform 500, attached to the platform 500, or otherwise communicatively coupled with the platform 500. The driver circuitry 546 may include individual drivers allowing other components of the platform 500 to interact with or control various input/output (I/O) devices that may be present within, or connected to, the platform 500. For example, driver circuitry 546 may include a display driver to control and allow access to a display device, a touchscreen driver to control and allow access to a touchscreen interface of the platform 500, sensor drivers to obtain sensor readings of sensor circuitry 521 and control and allow access to sensor circuitry 521, EMC drivers to obtain actuator positions of the EMCs 522 and/or control and allow access to the EMCs 522, a camera driver to control and allow access to an embedded image capture device, audio drivers to control and allow access to one or more audio devices.

The power management integrated circuitry (PMIC) 525 (also referred to as “power management circuitry 525”) may manage power provided to various components of the platform 500. In particular, with respect to the baseband circuitry 510, the PMIC 525 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion. The PMIC 525 may often be included when the platform 500 is capable of being powered by a battery 530, for example, when the device is included in a UE 101, 201, 301.

In some embodiments, the PMIC 525 may control, or otherwise be part of, various power saving mechanisms of the platform 500. For example, if the platform 500 is in an RRC_Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the platform 500 may power down for brief intervals of time and thus save power. If there is no data traffic activity for an extended period of time, then the platform 500 may transition off to an RRC_Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The platform 500 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again. The platform 500 may not receive data in this state; in order to receive data, it must transition back to RRC_Connected state. An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.

A battery 530 may power the platform 500, although in some examples the platform 500 may be mounted deployed in a fixed location, and may have a power supply coupled to an electrical grid. The battery 530 may be a lithium ion battery, a metal-air battery, such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, and the like. In some implementations, such as in V2X applications, the battery 530 may be a typical lead-acid automotive battery.

In some implementations, the battery 530 may be a “smart battery,” which includes or is coupled with a Battery Management System (BMS) or battery monitoring integrated circuitry. The BMS may be included in the platform 500 to track the state of charge (SoCh) of the battery 530. The BMS may be used to monitor other parameters of the battery 530 to provide failure predictions, such as the state of health (SoH) and the state of function (SoF) of the battery 530. The BMS may communicate the information of the battery 530 to the application circuitry 505 or other components of the platform 500. The BMS may also include an analog-to-digital (ADC) convertor that allows the application circuitry 505 to directly monitor the voltage of the battery 530 or the current flow from the battery 530. The battery parameters may be used to determine actions that the platform 500 may perform, such as transmission frequency, network operation, sensing frequency, and the like.

A power block, or other power supply coupled to an electrical grid may be coupled with the BMS to charge the battery 530. In some examples, the power block XS30 may be replaced with a wireless power receiver to obtain the power wirelessly, for example, through a loop antenna in the computer platform 500. In these examples, a wireless battery charging circuit may be included in the BMS. The specific charging circuits chosen may depend on the size of the battery 530, and thus, the current required. The charging may be performed using the Airfuel standard promulgated by the Airfuel Alliance, the Qi wireless charging standard promulgated by the Wireless Power Consortium, or the Rezence charging standard promulgated by the Alliance for Wireless Power, among others.

User interface circuitry 550 includes various input/output (I/O) devices present within, or connected to, the platform 500, and includes one or more user interfaces designed to enable user interaction with the platform 500 and/or peripheral component interfaces designed to enable peripheral component interaction with the platform 500. The user interface circuitry 550 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual means for accepting an input including, inter alia, one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, keypad, mouse, touchpad, touchscreen, microphones, scanner, headset, and/or the like. The output device circuitry includes any physical or virtual means for showing information or otherwise conveying information, such as sensor readings, actuator position(s), or other like information. Output device circuitry may include any number and/or combinations of audio or visual display, including, inter alia, one or more simple visual outputs/indicators (e.g., binary status indicators (e.g., light emitting diodes (LEDs)) and multi-character visual outputs, or more complex outputs such as display devices or touchscreens (e.g., Liquid Chrystal Displays (LCD), LED displays, quantum dot displays, projectors, etc.), with the output of characters, graphics, multimedia objects, and the like being generated or produced from the operation of the platform 500. The output device circuitry may also include speakers or other audio emitting devices, printer(s), and/or the like. In some embodiments, the sensor circuitry 521 may be used as the input device circuitry (e.g., an image capture device, motion capture device, or the like) and one or more EMCs may be used as the output device circuitry (e.g., an actuator to provide haptic feedback or the like). In another example, NFC circuitry including an NFC controller coupled with an antenna element and a processing device may be included to read electronic tags and/or connect with another NFC-enabled device. Peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a USB port, an audio jack, a power supply interface, etc.

Although not shown, the components of platform 500 may communicate with one another using a suitable bus or interconnect (IX) technology, which may include any number of technologies, including ISA, EISA, PCI, PCIx, PCIe, a Time-Trigger Protocol (TTP) system, a FlexRay system, or any number of other technologies. The bus/IX may be a proprietary bus/IX, for example, used in a SoC based system. Other bus/IX systems may be included, such as an I2C interface, an SPI interface, point-to-point interfaces, and a power bus, among others.

FIG. 6 illustrates example components of baseband circuitry 610 and radio front end modules (RFEM) 615 in accordance with various embodiments. The baseband circuitry 610 corresponds to the baseband circuitry 410 and 510 of FIGS. 4 and 5, respectively. The RFEM 615 corresponds to the RFEM 415 and 515 of FIGS. 4 and 5, respectively. As shown, the RFEMs 615 may include Radio Frequency (RF) circuitry 606, front-end module (FEM) circuitry 608, antenna array 611 coupled together at least as shown.

The baseband circuitry 610 includes circuitry and/or control logic configured to carry out various radio/network protocol and radio control functions that enable communication with one or more radio networks via the RF circuitry 606. The radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc. In some embodiments, modulation/demodulation circuitry of the baseband circuitry 610 may include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality. In some embodiments, encoding/decoding circuitry of the baseband circuitry 610 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality. Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments. The baseband circuitry 610 is configured to process baseband signals received from a receive signal path of the RF circuitry 606 and to generate baseband signals for a transmit signal path of the RF circuitry 606. The baseband circuitry 610 is configured to interface with application circuitry 405/505 (see FIGS. 4 and 5) for generation and processing of the baseband signals and for controlling operations of the RF circuitry 606. The baseband circuitry 610 may handle various radio control functions.

The aforementioned circuitry and/or control logic of the baseband circuitry 610 may include one or more single or multi-core processors. For example, the one or more processors may include a 3G baseband processor 604A, a 4G/LTE baseband processor 604B, a 5G/NR baseband processor 604C, or some other baseband processor(s) 604D for other existing generations, generations in development or to be developed in the future (e.g., sixth generation (6G), etc.). In other embodiments, some or all of the functionality of baseband processors 604A-D may be included in modules stored in the memory 604G and executed via a Central Processing Unit (CPU) 604E. In other embodiments, some or all of the functionality of baseband processors 604A-D may be provided as hardware accelerators (e.g., FPGAs, ASICs, etc.) loaded with the appropriate bit streams or logic blocks stored in respective memory cells. In various embodiments, the memory 604G may store program code of a real-time OS (RTOS), which when executed by the CPU 604E (or other baseband processor), is to cause the CPU 604E (or other baseband processor) to manage resources of the baseband circuitry 610, schedule tasks, etc. Examples of the RTOS may include Operating System Embedded (OSE)™ provided by Enea®, Nucleus RTOS™ provided by Mentor Graphics®, Versatile Real-Time Executive (VRTX) provided by Mentor Graphics®, ThreadX™ provided by Express Logic®, FreeRTOS, REX OS provided by Qualcomm®, OKL4 provided by Open Kernel (OK) Labs®, or any other suitable RTOS, such as those discussed in this document. In addition, the baseband circuitry 610 includes one or more audio digital signal processor(s) (DSP) 604F. The audio DSP(s) 604F include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments.

In some embodiments, each of the processors 604A-604E include respective memory interfaces to send/receive data to/from the memory 604G. The baseband circuitry 610 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as an interface to send/receive data to/from memory external to the baseband circuitry 610; an application circuitry interface to send/receive data to/from the application circuitry 405/505 of FIGS. 4-XT); an RF circuitry interface to send/receive data to/from RF circuitry 606 of FIG. 6; a wireless hardware connectivity interface to send/receive data to/from one or more wireless hardware elements (e.g., Near Field Communication (NFC) components, Bluetooth®/Bluetooth® Low Energy components, Wi-Fi® components, and/or the like); and a power management interface to send/receive power or control signals to/from the PMIC 525.

In alternate embodiments (which may be combined with the above described embodiments), baseband circuitry 610 includes one or more digital baseband systems, which are coupled with one another via an interconnect subsystem and to a CPU subsystem, an audio subsystem, and an interface subsystem. The digital baseband subsystems may also be coupled to a digital baseband interface and a mixed-signal baseband subsystem via another interconnect subsystem. Each of the interconnect subsystems may include a bus system, point-to-point connections, network-on-chip (NOC) structures, and/or some other suitable bus or interconnect technology, such as those discussed in this document. The audio subsystem may include DSP circuitry, buffer memory, program memory, speech processing accelerator circuitry, data converter circuitry such as analog-to-digital and digital-to-analog converter circuitry, analog circuitry including one or more of amplifiers and filters, and/or other like components. In an aspect of the present disclosure, baseband circuitry 610 may include protocol processing circuitry with one or more instances of control circuitry (not shown) to provide control functions for the digital baseband circuitry and/or radio frequency circuitry (e.g., the radio front end modules 615).

Although not shown by FIG. 6, in some embodiments, the baseband circuitry 610 includes individual processing device(s) to operate one or more wireless communication protocols (e.g., a “multi-protocol baseband processor” or “protocol processing circuitry”) and individual processing device(s) to implement PHY layer functions. In these embodiments, the PHY layer functions include the aforementioned radio control functions. In these embodiments, the protocol processing circuitry operates or implements various protocol layers/entities of one or more wireless communication protocols. In a first example, the protocol processing circuitry may operate LTE protocol entities and/or 5G/NR protocol entities when the baseband circuitry 610 and/or RF circuitry 606 are part of mmWave communication circuitry or some other suitable cellular communication circuitry. In the first example, the protocol processing circuitry would operate MAC, RLC, PDCP, SDAP, RRC, and NAS functions. In a second example, the protocol processing circuitry may operate one or more IEEE-based protocols when the baseband circuitry 610 and/or RF circuitry 606 are part of a Wi-Fi communication system. In the second example, the protocol processing circuitry would operate Wi-Fi MAC and logical link control (LLC) functions. The protocol processing circuitry may include one or more memory structures (e.g., 604G) to store program code and data for operating the protocol functions, as well as one or more processing cores to execute the program code and perform various operations using the data. The baseband circuitry 610 may also support radio communications for more than one wireless protocol.

The various hardware elements of the baseband circuitry 610 discussed in this document may be implemented, for example, as a solder-down substrate including one or more integrated circuits (ICs), a single packaged IC soldered to a main circuit board or a multi-chip module containing two or more ICs. In one example, the components of the baseband circuitry 610 may be suitably combined in a single chip or chipset, or disposed on a same circuit board. In another example, some or all of the constituent components of the baseband circuitry 610 and RF circuitry 606 may be implemented together such as, for example, a system on a chip (SoC) or System-in-Package (SiP). In another example, some or all of the constituent components of the baseband circuitry 610 may be implemented as a separate SoC that is communicatively coupled with and RF circuitry 606 (or multiple instances of RF circuitry 606). In yet another example, some or all of the constituent components of the baseband circuitry 610 and the application circuitry 405/505 may be implemented together as individual SoCs mounted to a same circuit board (e.g., a “multi-chip package”).

In some embodiments, the baseband circuitry 610 may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 610 may support communication with an E-UTRAN or other WMAN, a WLAN, a WPAN. Embodiments in which the baseband circuitry 610 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

RF circuitry 606 enables communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 606 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry 606 may include a receive signal path, which may include circuitry to down-convert RF signals received from the FEM circuitry 608 and provide baseband signals to the baseband circuitry 610. RF circuitry 606 may also include a transmit signal path, which may include circuitry to up-convert baseband signals provided by the baseband circuitry 610 and provide RF output signals to the FEM circuitry 608 for transmission.

In some embodiments, the receive signal path of the RF circuitry 606 includes mixer circuitry 606 a, amplifier circuitry 606 b and filter circuitry 606 c. In some embodiments, the transmit signal path of the RF circuitry 606 may include filter circuitry 606 c and mixer circuitry 606 a. RF circuitry 606 may also include synthesizer circuitry 606 d for synthesizing a frequency for use by the mixer circuitry 606 a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 606 a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 608 based on the synthesized frequency provided by synthesizer circuitry 606 d. The amplifier circuitry 606 b may be configured to amplify the down-converted signals and the filter circuitry 606 c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals may be provided to the baseband circuitry 610 for further processing. In some embodiments, the output baseband signals may be zero-frequency baseband signals, although this is not a requirement. In some embodiments, mixer circuitry 606 a of the receive signal path may include passive mixers, although the scope of the embodiments is not limited in this respect.

In some embodiments, the mixer circuitry 606 a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 606 d to generate RF output signals for the FEM circuitry 608. The baseband signals may be provided by the baseband circuitry 610 and may be filtered by filter circuitry 606 c.

In some embodiments, the mixer circuitry 606 a of the receive signal path and the mixer circuitry 606 a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively. In some embodiments, the mixer circuitry 606 a of the receive signal path and the mixer circuitry 606 a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 606 a of the receive signal path and the mixer circuitry 606 a of the transmit signal path may be arranged for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuitry 606 a of the receive signal path and the mixer circuitry 606 a of the transmit signal path may be configured for super-heterodyne operation.

In some embodiments, the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternate embodiments, the output baseband signals and the input baseband signals may be digital baseband signals. In these alternate embodiments, the RF circuitry 606 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 610 may include a digital baseband interface to communicate with the RF circuitry 606.

In some dual-mode embodiments, a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.

In some embodiments, the synthesizer circuitry 606 d may be a fractional-N synthesizer or a fractional N/N+1 synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, synthesizer circuitry 606 d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

The synthesizer circuitry 606 d may be configured to synthesize an output frequency for use by the mixer circuitry 606 a of the RF circuitry 606 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 606 d may be a fractional N/N+1 synthesizer.

In some embodiments, frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement. Divider control input may be provided by either the baseband circuitry 610 or the application circuitry 405/505 depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the application circuitry 405/505.

Synthesizer circuitry 606 d of the RF circuitry 606 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator. In some embodiments, the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by either N or N+1 (e.g., based on a carry out) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop. In these embodiments, the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

In some embodiments, synthesizer circuitry 606 d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some embodiments, the output frequency may be a LO frequency (fLO). In some embodiments, the RF circuitry 606 may include an IQ/polar converter.

FEM circuitry 608 may include a receive signal path, which may include circuitry configured to operate on RF signals received from antenna array 611, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 606 for further processing. FEM circuitry 608 may also include a transmit signal path, which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 606 for transmission by one or more of antenna elements of antenna array 611. In various embodiments, the amplification through the transmit or receive signal paths may be done solely in the RF circuitry 606, solely in the FEM circuitry 608, or in both the RF circuitry 606 and the FEM circuitry 608.

In some embodiments, the FEM circuitry 608 may include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry 608 may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry 608 may include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 606). The transmit signal path of the FEM circuitry 608 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 606), and one or more filters to generate RF signals for subsequent transmission by one or more antenna elements of the antenna array 611.

The antenna array 611 includes one or more antenna elements, each of which is configured convert electrical signals into radio waves to travel through the air and to convert received radio waves into electrical signals. For example, digital baseband signals provided by the baseband circuitry 610 is converted into analog RF signals (e.g., modulated waveform) that will be amplified and transmitted via the antenna elements of the antenna array 611 including one or more antenna elements (not shown). The antenna elements may be omnidirectional, direction, or a combination thereof. The antenna elements may be formed in a multitude of arranges as are known and/or discussed in this document. The antenna array 611 may include microstrip antennas or printed antennas that are fabricated on the surface of one or more printed circuit boards. The antenna array 611 may be formed in as a patch of metal foil (e.g., a patch antenna) in a variety of shapes, and may be coupled with the RF circuitry 606 and/or FEM circuitry 608 using metal transmission lines or the like.

Processors of the application circuitry 405/505 and processors of the baseband circuitry 610 may be used to execute elements of one or more instances of a protocol stack. For example, processors of the baseband circuitry 610, alone or in combination, may be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 405/505 may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., TCP and UDP layers). As referred to in this document, Layer 3 may include a RRC layer, described in further detail below. As referred to in this document, Layer 2 may include a MAC layer, an RLC layer, and a PDCP layer, described in further detail below. As referred to in this document, Layer 1 may include a PHY layer of a UE/RAN node, described in further detail below.

FIG. 7 illustrates an example block diagram of cellular communication circuitry 560. It is noted that the block diagram of the cellular communication circuitry 560 of FIG. 7 is an example of a cellular communication circuit, but that other configurations are also possible. In some implementations, the cellular communication circuitry 560 may be included in a communication device, such as the platform 500 described above. As noted above, platform 500 may be a UE device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet, a wireless sensor, surveillance equipment, or wearables devices, or a combination of them, among other devices.

The cellular communication circuitry 560 may couple (e.g., communicatively, directly, or indirectly) to one or more antennas, such as antennas of antenna array 611 as shown (e.g., in FIG. 6). In some implementations, the cellular communication circuitry 560 includes or is communicatively coupled to dedicated receive chains, processors, or radios for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G NR). For example, as shown in FIG. 7, cellular communication circuitry 560 may include a modem 710 and a modem 720. Modem 710 may be configured for communications according to a first RAT, e.g., such as LTE or LTE-A, and modem 720 may be configured for communications according to a second RAT, e.g., such as 5G NR.

The modem 710 includes one or more processors 712 and a memory 716 in communication with the processors 712. The modem 710 is in communication with a radio frequency front end module 515 a (e.g., RFEM 515). The RFEM 515 a may include circuitry for transmitting and receiving radio signals. For example, the RF front end 730 includes receive circuitry (RX) 732 and transmit circuitry (TX) 734. In some implementations, the receive circuitry 732 is in communication with downlink (DL) front end 750, which may include circuitry for receiving radio signals via antenna 611 a.

Similarly, the modem 720 includes one or more processors 722 and a memory 726 in communication with the processors 722. The modem 720 is in communication with an RFEM 515 b. The RFEM 515 b may include circuitry for transmitting and receiving radio signals. For example, the RF front end 740 may include receive circuitry 742 and transmit circuitry 744. In some implementations, the receive circuitry 742 is in communication with DL front end 760, which may include circuitry for receiving radio signals via antenna 611 b.

The modem 710 may include hardware and software components for implementing the above features or for time division multiplexing UL data for NSA NR operations, as well as the various other techniques described in this document. The processors 712 may be configured to implement part or all of the features described in this document, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), the processor 712 may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit). Alternatively (or in addition) the processor 712, in conjunction with one or more of the other components 730, 732, 734, 750, 770, 772, and 611 may be configured to implement some or all of the features described in this document.

The processors 712 may include one or more processing elements. Thus, processors 712 may include one or more integrated circuits (ICs) that are configured to perform the functions of processors 712. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processors 712.

The modem 720 may include hardware and software components for implementing the above features for time division multiplexing UL data for NSA NR operations, as well as the various other techniques described in this document. The processors 722 may be configured to implement part or all of the features described in this document, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), processor 722 may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit). Alternatively (or in addition) the processor 722, in conjunction with one or more of the other components 740, 742, 744, 750, 770, 772, and 611 may be configured to implement part or all of the features described in this document.

In addition, the processors 722 may include one or more processing elements. Thus, the processors 722 may include one or more integrated circuits (ICs) that are configured to perform the functions of processors 722. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processors 722.

FIG. 8 is a block diagram illustrating example protocol functions for implementing in a wireless communication device according to various embodiments. In particular, FIG. 8 includes an arrangement 800 showing interconnections between various protocol layers/entities. The following description of FIG. 8 is provided for various protocol layers/entities that operate in conjunction with the 5G/NR system standards and LTE system standards, but some or all of the aspects of FIG. 8 may be applicable to other wireless communication network systems as well.

The protocol layers of arrangement 800 may include one or more of PHY 810, MAC 820, RLC 830, PDCP 840, SDAP 847, RRC 855, and NAS layer 857, in addition to other higher layer functions not illustrated. The protocol layers may include one or more service access points (e.g., items 859, 856, 850, 849, 845, 835, 825, and 815 in FIG. 8) that may provide communication between two or more protocol layers.

The PHY 810 may transmit and receive physical layer signals 805 that may be received from or transmitted to one or more other communication devices. The physical layer signals 805 may include one or more physical channels, such as those discussed in this document. The PHY 810 may further perform link adaptation or adaptive modulation and coding (AMC), power control, cell search (e.g., for initial synchronization and handover purposes), and other measurements used by higher layers, such as the RRC 855. The PHY 810 may still further perform error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, modulation/demodulation of physical channels, interleaving, rate matching, mapping onto physical channels, and MIMO antenna processing. In embodiments, an instance of PHY 810 may process requests from and provide indications to an instance of MAC 820 via one or more PHY-SAP 815. According to some embodiments, requests and indications communicated via PHY-SAP 815 may include one or more transport channels.

Instance(s) of MAC 820 may process requests from, and provide indications to, an instance of RLC 830 via one or more MAC-SAPs 825. These requests and indications communicated via the MAC-SAP 825 may include one or more logical channels. The MAC 820 may perform mapping between the logical channels and transport channels, multiplexing of MAC SDUs from one or more logical channels onto TBs to be delivered to PHY 810 via the transport channels, de-multiplexing MAC SDUs to one or more logical channels from TBs delivered from the PHY 810 via transport channels, multiplexing MAC SDUs onto TBs, scheduling information reporting, error correction through HARQ, and logical channel prioritization.

Instance(s) of RLC 830 may process requests from and provide indications to an instance of PDCP 840 via one or more radio link control service access points (RLC-SAP) 835. These requests and indications communicated via RLC-SAP 835 may include one or more RLC channels. The RLC 830 may operate in a plurality of modes of operation, including: Transparent Mode™, Unacknowledged Mode (UM), and Acknowledged Mode (AM). The RLC 830 may execute transfer of upper layer protocol data units (PDUs), error correction through automatic repeat request (ARQ) for AM data transfers, and concatenation, segmentation and reassembly of RLC SDUs for UM and AM data transfers. The RLC 830 may also execute re-segmentation of RLC data PDUs for AM data transfers, reorder RLC data PDUs for UM and AM data transfers, detect duplicate data for UM and AM data transfers, discard RLC SDUs for UM and AM data transfers, detect protocol errors for AM data transfers, and perform RLC re-establishment.

Instance(s) of PDCP 840 may process requests from and provide indications to instance(s) of RRC 855 and/or instance(s) of SDAP 847 via one or more packet data convergence protocol service access points (PDCP-SAP) 845. These requests and indications communicated via PDCP-SAP 845 may include one or more radio bearers. The PDCP 840 may execute header compression and decompression of IP data, maintain PDCP Sequence Numbers (SNs), perform in-sequence delivery of upper layer PDUs at re-establishment of lower layers, eliminate duplicates of lower layer SDUs at re-establishment of lower layers for radio bearers mapped on RLC AM, cipher and decipher control plane data, perform integrity protection and integrity verification of control plane data, control timer-based discard of data, and perform security operations (e.g., ciphering, deciphering, integrity protection, integrity verification, etc.).

Instance(s) of SDAP 847 may process requests from and provide indications to one or more higher layer protocol entities via one or more SDAP-SAP 849. These requests and indications communicated via SDAP-SAP 849 may include one or more QoS flows. The SDAP 847 may map QoS flows to DRBs, and vice versa, and may also mark QFIs in DL and UL packets. A single SDAP entity 847 may be configured for an individual PDU session. In the UL direction, the NG-RAN 110 may control the mapping of QoS Flows to DRB(s) in two different ways, reflective mapping or explicit mapping. For reflective mapping, the SDAP 847 of a UE 101 may monitor the QFIs of the DL packets for each DRB, and may apply the same mapping for packets flowing in the UL direction. For a DRB, the SDAP 847 of the UE 101 may map the UL packets belonging to the QoS flows(s) corresponding to the QoS flow ID(s) and PDU session observed in the DL packets for that DRB. To enable reflective mapping, the NG-RAN 310 may mark DL packets over the Uu interface with a QoS flow ID. The explicit mapping may involve the RRC 855 configuring the SDAP 847 with an explicit QoS flow to DRB mapping rule, which may be stored and followed by the SDAP 847. In embodiments, the SDAP 847 may only be used in NR implementations and may not be used in LTE implementations.

The RRC 855 may configure, via one or more management service access points (M-SAP), aspects of one or more protocol layers, which may include one or more instances of PHY 810, MAC 820, RLC 830, PDCP 840 and SDAP 847. In embodiments, an instance of RRC 855 may process requests from and provide indications to one or more NAS entities 857 via one or more RRC-SAPs 856. The main services and functions of the RRC 855 may include broadcast of system information (e.g., included in MIBs or SIBs related to the NAS), broadcast of system information related to the access stratum (AS), paging, establishment, maintenance and release of an RRC connection between the UE 101 and RAN 110 (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), establishment, configuration, maintenance and release of point to point Radio Bearers, security functions including key management, inter-RAT mobility, and measurement configuration for UE measurement reporting. The MIBs and SIBs may include one or more IEs, which may each include individual data fields or data structures.

The NAS 857 may form the highest stratum of the control plane between the UE 101 and the AMF 321. The NAS 857 may support the mobility of the UEs 101 and the session management procedures to establish and maintain IP connectivity between the UE 101 and a P-GW in LTE systems.

According to various embodiments, one or more protocol entities of arrangement 800 may be implemented in UEs 101, RAN nodes 111, AMF 321 in NR implementations or MME 221 in LTE implementations, UPF 302 in NR implementations or S-GW 222 and P-GW 223 in LTE implementations, or the like to be used for control plane or user plane communications protocol stack between the aforementioned devices. In such embodiments, one or more protocol entities that may be implemented in one or more of UE 101, gNB 111, AMF 321, etc. may communicate with a respective peer protocol entity that may be implemented in or on another device using the services of respective lower layer protocol entities to perform such communication. In some embodiments, a gNB-CU of the gNB 111 may host the RRC 855, SDAP 847, and PDCP 840 of the gNB that controls the operation of one or more gNB-DUs, and the gNB-DUs of the gNB 111 may each host the RLC 830, MAC 820, and PHY 810 of the gNB 111.

In a first example, a control plane protocol stack may include, in order from highest layer to lowest layer, NAS 857, RRC 855, PDCP 840, RLC 830, MAC 820, and PHY 810. In this example, upper layers 860 may be built on top of the NAS 857, which includes an IP layer 861, an SCTP 862, and an application layer signaling protocol (AP) 863.

In NR implementations, the AP 863 may be an NG application protocol layer (NGAP or NG-AP) 863 for the NG interface 113 defined between the NG-RAN node 111 and the AMF 321, or the AP 863 may be an Xn application protocol layer (XnAP or Xn-AP) 863 for the Xn interface 112 that is defined between two or more RAN nodes 111.

The NG-AP 863 may support the functions of the NG interface 113 and may include Elementary Procedures (EPs). An NG-AP EP may be a unit of interaction between the NG-RAN node 111 and the AMF 321. The NG-AP 863 services may include two groups: UE-associated services (e.g., services related to a UE 101) and non-UE-associated services (e.g., services related to the whole NG interface instance between the NG-RAN node 111 and AMF 321). These services may include functions including, but not limited to: a paging function for the sending of paging requests to NG-RAN nodes 111 involved in a particular paging area; a UE context management function for allowing the AMF 321 to establish, modify, and/or release a UE context in the AMF 321 and the NG-RAN node 111; a mobility function for UEs 101 in ECM-CONNECTED mode for intra-system HOs to support mobility within NG-RAN and inter-system HOs to support mobility from/to EPS systems; a NAS Signaling Transport function for transporting or rerouting NAS messages between UE 101 and AMF 321; a NAS node selection function for determining an association between the AMF 321 and the UE 101; NG interface management function(s) for setting up the NG interface and monitoring for errors over the NG interface; a warning message transmission function for providing means to transfer warning messages via NG interface or cancel ongoing broadcast of warning messages; a Configuration Transfer function for requesting and transferring of RAN configuration information (e.g., SON information, performance measurement (PM) data, etc.) between two RAN nodes 111 via CN 120; and/or other like functions.

The XnAP 863 may support the functions of the Xn interface 112 and may include XnAP basic mobility procedures and XnAP global procedures. The XnAP basic mobility procedures may include procedures used to handle UE mobility within the NG RAN 111 (or E-UTRAN 210), such as handover preparation and cancellation procedures, SN Status Transfer procedures, UE context retrieval and UE context release procedures, RAN paging procedures, dual connectivity related procedures, and the like. The XnAP global procedures may include procedures that are not related to a specific UE 101, such as Xn interface setup and reset procedures, NG-RAN update procedures, cell activation procedures, and the like.

In LTE implementations, the AP 863 may be an S1 Application Protocol layer (S1-AP) 863 for the S1 interface 113 defined between an E-UTRAN node 111 and an MME, or the AP 863 may be an X2 application protocol layer (X2AP or X2-AP) 863 for the X2 interface 112 that is defined between two or more E-UTRAN nodes 111.

The S1 Application Protocol layer (S1-AP) 863 may support the functions of the S1 interface, and similar to the NG-AP discussed previously, the S1-AP may include S1-AP EPs. An S1-AP EP may be a unit of interaction between the E-UTRAN node 111 and an MME 221 within an LTE CN 120. The S1-AP 863 services may include two groups: UE-associated services and non UE-associated services. These services perform functions including, but not limited to: E-UTRAN Radio Access Bearer (E-RAB) management, UE capability indication, mobility, NAS signaling transport, RAN Information Management (RIM), and configuration transfer.

The X2AP 863 may support the functions of the X2 interface 112 and may include X2AP basic mobility procedures and X2AP global procedures. The X2AP basic mobility procedures may include procedures used to handle UE mobility within the E-UTRAN 120, such as handover preparation and cancellation procedures, SN Status Transfer procedures, UE context retrieval and UE context release procedures, RAN paging procedures, dual connectivity related procedures, and the like. The X2AP global procedures may include procedures that are not related to a specific UE 101, such as X2 interface setup and reset procedures, load indication procedures, error indication procedures, cell activation procedures, and the like.

The SCTP layer (alternatively referred to as the SCTP/IP layer) 862 may provide guaranteed delivery of application layer messages (e.g., NGAP or XnAP messages in NR implementations, or S1-AP or X2AP messages in LTE implementations). The SCTP 862 may ensure reliable delivery of signaling messages between the RAN node 111 and the AMF 321/MME 221 based, in part, on the IP protocol, supported by the IP 861. The Internet Protocol layer (IP) 861 may be used to perform packet addressing and routing functionality. In some implementations the IP layer 861 may use point-to-point transmission to deliver and convey PDUs. In this regard, the RAN node 111 may include L2 and L1 layer communication links (e.g., wired or wireless) with the MME/AMF to exchange information.

In a second example, a user plane protocol stack may include, in order from highest layer to lowest layer, SDAP 847, PDCP 840, RLC 830, MAC 820, and PHY 810. The user plane protocol stack may be used for communication between the UE 101, the RAN node 111, and UPF 302 in NR implementations or an S-GW 222 and P-GW 223 in LTE implementations. In this example, upper layers 851 may be built on top of the SDAP 847, and may include a user datagram protocol (UDP) and IP security layer (UDP/IP) 852, a General Packet Radio Service (GPRS) Tunneling Protocol for the user plane layer (GTP-U) 853, and a User Plane PDU layer (UP PDU) 863.

The transport network layer 854 (also referred to as a “transport layer”) may be built on IP transport, and the GTP-U 853 may be used on top of the UDP/IP layer 852 (including a UDP layer and IP layer) to carry user plane PDUs (UP-PDUs). The IP layer (also referred to as the “Internet layer”) may be used to perform packet addressing and routing functionality. The IP layer may assign IP addresses to user data packets in any of IPv4, IPv6, or PPP formats, for example.

The GTP-U 853 may be used for carrying user data within the GPRS core network and between the radio access network and the core network. The user data transported can be packets in any of IPv4, IPv6, or PPP formats, for example. The UDP/IP 852 may provide checksums for data integrity, port numbers for addressing different functions at the source and destination, and encryption and authentication on the selected data flows. The RAN node 111 and the S-GW 222 may utilize an S1-U interface to exchange user plane data via a protocol stack including an L1 layer (e.g., PHY 810), an L2 layer (e.g., MAC 820, RLC 830, PDCP 840, and/or SDAP 847), the UDP/IP layer 852, and the GTP-U 853. The S-GW 222 and the P-GW 223 may utilize an S5/S8a interface to exchange user plane data via a protocol stack including an L1 layer, an L2 layer, the UDP/IP layer 852, and the GTP-U 853. As discussed previously, NAS protocols may support the mobility of the UE 101 and the session management procedures to establish and maintain IP connectivity between the UE 101 and the P-GW 223.

Moreover, although not shown by FIG. 8, an application layer may be present above the AP 863 and/or the transport network layer 854. The application layer may be a layer in which a user of the UE 101, RAN node 111, or other network element interacts with software applications being executed, for example, by application circuitry 405 or application circuitry 505, respectively. The application layer may also provide one or more interfaces for software applications to interact with communications systems of the UE 101 or RAN node 111, such as the baseband circuitry 610. In some implementations the IP layer and/or the application layer may provide the same or similar functionality as layers 5-7, or portions thereof, of the Open Systems Interconnection (OSI) model (e.g., OSI Layer 7—the application layer, OSI Layer 6—the presentation layer, and OSI Layer 5 the session layer).

FIG. 9 illustrates components of a core network in accordance with various embodiments. The components of the CN 220 may be implemented in one physical node or separate physical nodes including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In embodiments, the components of CN 320 may be implemented in a same or similar manner as discussed in this document with regard to the components of CN 220. In some embodiments, NFV is utilized to virtualize any or all of the above-described network node functions via executable instructions stored in one or more computer-readable storage mediums (described in further detail below). A logical instantiation of the CN 220 may be referred to as a network slice 901, and individual logical instantiations of the CN 220 may provide specific network capabilities and network characteristics. A logical instantiation of a portion of the CN 220 may be referred to as a network sub-slice 902 (e.g., the network sub-slice 902 is shown to include the P-GW 223 and the PCRF 226).

As used in this document, the terms “instantiate,” “instantiation,” and the like may refer to the creation of an instance, and an “instance” may refer to a concrete occurrence of an object, which may occur, for example, during execution of program code. A network instance may refer to information identifying a domain, which may be used for traffic detection and routing in case of different IP domains or overlapping IP addresses. A network slice instance may refer to a set of network functions (NFs) instances and the resources (e.g., compute, storage, and networking resources) required to deploy the network slice.

With respect to 5G systems (see, e.g., FIG. 3), a network slice always includes a RAN part and a CN part. The support of network slicing relies on the principle that traffic for different slices is handled by different PDU sessions. The network can realize the different network slices by scheduling and also by providing different L1/L2 configurations. The UE 301 provides assistance information for network slice selection in an appropriate RRC message, if it has been provided by NAS. While the network can support large number of slices, the UE need not support more than 8 slices simultaneously.

A network slice may include the CN 320 control plane and user plane NFs, NG-RANs 310 in a serving PLMN, and a N3IWF functions in the serving PLMN. Individual network slices may have different S-NSSAI and/or may have different SSTs. NSSAI includes one or more S-NSSAIs, and each network slice is uniquely identified by an S-NSSAI. Network slices may differ for supported features and network functions optimizations, and/or multiple network slice instances may deliver the same service/features but for different groups of UEs 301 (e.g., enterprise users). For example, individual network slices may deliver different committed service(s) and/or may be dedicated to a particular customer or enterprise. In this example, each network slice may have different S-NSSAIs with the same SST but with different slice differentiators. Additionally, a single UE may be served with one or more network slice instances simultaneously via a 5G AN and associated with eight different S-NSSAIs. Moreover, an AMF 321 instance serving an individual UE 301 may belong to each of the network slice instances serving that UE.

Network Slicing in the NG-RAN 310 involves RAN slice awareness. RAN slice awareness includes differentiated handling of traffic for different network slices, which have been pre-configured. Slice awareness in the NG-RAN 310 is introduced at the PDU session level by indicating the S-NSSAI corresponding to a PDU session in all signaling that includes PDU session resource information. How the NG-RAN 310 supports the slice enabling in terms of NG-RAN functions (e.g., the set of network functions that include each slice) is implementation dependent. The NG-RAN 310 selects the RAN part of the network slice using assistance information provided by the UE 301 or the 5GC 320, which unambiguously identifies one or more of the pre-configured network slices in the PLMN. The NG-RAN 310 also supports resource management and policy enforcement between slices as per SLAs. A single NG-RAN node may support multiple slices, and the NG-RAN 310 may also apply an appropriate RRM policy for the SLA in place to each supported slice. The NG-RAN 310 may also support QoS differentiation within a slice.

The NG-RAN 310 may also use the UE assistance information for the selection of an AMF 321 during an initial attach, if available. The NG-RAN 310 uses the assistance information for routing the initial NAS to an AMF 321. If the NG-RAN 310 is unable to select an AMF 321 using the assistance information, or the UE 301 does not provide any such information, the NG-RAN 310 sends the NAS signaling to a default AMF 321, which may be among a pool of AMFs 321. For subsequent accesses, the UE 301 provides a temp ID, which is assigned to the UE 301 by the 5GC 320, to enable the NG-RAN 310 to route the NAS message to the appropriate AMF 321 as long as the temp ID is valid. The NG-RAN 310 is aware of, and can reach, the AMF 321 that is associated with the temp ID. Otherwise, the method for initial attach applies.

The NG-RAN 310 supports resource isolation between slices. NG-RAN 310 resource isolation may be achieved by means of RRM policies and protection mechanisms that should avoid that shortage of shared resources if one slice breaks the service level agreement for another slice. In some implementations, it is possible to fully dedicate NG-RAN 310 resources to a certain slice. How NG-RAN 310 supports resource isolation is implementation dependent.

Some slices may be available only in part of the network. Awareness in the NG-RAN 310 of the slices supported in the cells of its neighbors may be beneficial for inter-frequency mobility in connected mode. The slice availability may not change within the UE's registration area. The NG-RAN 310 and the 5GC 320 are responsible to handle a service request for a slice that may or may not be available in a given area. Admission or rejection of access to a slice may depend on factors such as support for the slice, availability of resources, support of the requested service by NG-RAN 310.

The UE 301 may be associated with multiple network slices simultaneously. In case the UE 301 is associated with multiple slices simultaneously, only one signaling connection is maintained, and for intra-frequency cell reselection, the UE 301 tries to camp on the best cell. For inter-frequency cell reselection, dedicated priorities can be used to control the frequency on which the UE 301 camps. The 5GC 320 is to validate that the UE 301 has the rights to access a network slice. Prior to receiving an Initial Context Setup Request message, the NG-RAN 310 may be allowed to apply some provisional/local policies, based on awareness of a particular slice that the UE 301 is requesting to access. During the initial context setup, the NG-RAN 310 is informed of the slice for which resources are being requested.

FIG. 10 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed in this document. Specifically, FIG. 10 shows a diagrammatic representation of hardware resources 1000 including one or more processors (or processor cores) 1010, one or more memory/storage devices 1020, and one or more communication resources 1030, each of which may be communicatively coupled via a bus 1040. For embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 1002 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 1000.

The processors 1010 may include, for example, a processor 1012 and a processor 1014. The processor(s) 1010 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio-frequency integrated circuit (RFIC), another processor (including those discussed in this document), or any suitable combination thereof.

The memory/storage devices 1020 may include main memory, disk storage, or any suitable combination thereof. The memory/storage devices 1020 may include, but are not limited to, any type of volatile or nonvolatile memory such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc.

The communication resources 1030 may include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices 1004 or one or more databases 1006 via a network 1008. For example, the communication resources 1030 may include wired communication components (e.g., for coupling via USB), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components.

Instructions 1050 may include software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 1010 to perform any one or more of the methodologies discussed in this document. The instructions 1050 may reside, completely or partially, within at least one of the processors 1010 (e.g., within the processor's cache memory), the memory/storage devices 1020, or any suitable combination thereof. Furthermore, any portion of the instructions 1050 may be transferred to the hardware resources 1000 from any combination of the peripheral devices 1004 or the databases 1006. Accordingly, the memory of processors 1010, the memory/storage devices 1020, the peripheral devices 1004, and the databases 1006 are examples of computer-readable and machine-readable media.

Generally, the term “circuitry” as used in this document refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide the described functionality. In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.

The term “processor circuitry” as used in this document refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and/or transferring digital data. The term “processor circuitry” may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and/or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and/or functional processes. The terms “application circuitry” and/or “baseband circuitry” may be considered synonymous to, and may be referred to as, “processor circuitry.”

The term “interface circuitry” as used in this document refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term “interface circuitry” may refer to one or more hardware interfaces, for example, buses, I/O interfaces, peripheral component interfaces, network interface cards, and/or the like.

The term “user equipment” or “UE” as used in this document refers to a device with radio communication capabilities and may describe a remote user of network resources in a communications network. The term “user equipment” or “UE” may be considered synonymous to, and may be referred to as, client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the term “user equipment” or “UE” may include any type of wireless/wired device or any computing device including a wireless communications interface.

The term “network element” as used in this document refers to physical or virtualized equipment and/or infrastructure used to provide wired or wireless communication network services. The term “network element” may be considered synonymous to and/or referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVL, and/or the like.

The term “computer system” as used in this document refers to any type interconnected electronic devices, computer devices, or components thereof. Additionally, the term “computer system” and/or “system” may refer to various components of a computer that are communicatively coupled with one another. Furthermore, the term “computer system” and/or “system” may refer to multiple computer devices and/or multiple computing systems that are communicatively coupled with one another and configured to share computing and/or networking resources.

The term “appliance,” “computer appliance,” or the like, as used in this document refers to a computer device or computer system with program code (e.g., software or firmware) that is specifically designed to provide a specific computing resource. A “virtual appliance” is a virtual machine image to be implemented by a hypervisor-equipped device that virtualizes or emulates a computer appliance or otherwise is dedicated to provide a specific computing resource.

The term “resource” as used in this document refers to a physical or virtual device, a physical or virtual component within a computing environment, and/or a physical or virtual component within a particular device, such as computer devices, mechanical devices, memory space, processor/CPU time, processor/CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input/output operations, ports or network sockets, channel/link allocation, throughput, memory usage, storage, network, database and applications, workload units, and/or the like. A “hardware resource” may refer to compute, storage, and/or network resources provided by physical hardware element(s). A “virtualized resource” may refer to compute, storage, and/or network resources provided by virtualization infrastructure to an application, device, system, etc. The term “network resource” or “communication resource” may refer to resources that are accessible by computer devices/systems via a communications network. The term “system resources” may refer to any kind of shared entities to provide services, and may include computing and/or network resources. System resources may be considered as a set of coherent functions, network data objects or services, accessible through a server where such system resources reside on a single host or multiple hosts and are clearly identifiable.

The term “channel” as used in this document refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream. The term “channel” may be synonymous with and/or equivalent to “communications channel,” “data communications channel,” “transmission channel,” “data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radiofrequency carrier,” and/or any other like term denoting a pathway or medium through which data is communicated. Additionally, the term “link” as used in this document refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information.

The terms “instantiate,” “instantiation,” and the like as used in this document refers to the creation of an instance. An “instance” also refers to a concrete occurrence of an object, which may occur, for example, during execution of program code.

The terms “coupled,” “communicatively coupled,” along with derivatives thereof are used in this document. The term “coupled” may mean two or more elements are in direct physical or electrical contact with one another, may mean that two or more elements indirectly contact each other but still cooperate or interact with each other, and/or may mean that one or more other elements are coupled or connected between the elements that are said to be coupled with each other. The term “directly coupled” may mean that two or more elements are in direct contact with one another. The term “communicatively coupled” may mean that two or more elements may be in contact with one another by a means of communication including through a wire or other interconnect connection, through a wireless communication channel or ink, and/or the like.

The term “information element” refers to a structural element containing one or more fields. The term “field” refers to individual contents of an information element, or a data element that contains content. The term “SMTC” refers to an SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration.

The term “SSB” refers to an SS/PBCH block. The term “a “Primary Cell” refers to the MCG cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure. The term “Primary SCG Cell” refers to the SCG cell in which the UE performs random access when performing the Reconfiguration with Sync procedure for DC operation. The term “Secondary Cell” refers to a cell providing additional radio resources on top of a special cell for a UE configured with CA. The term “Secondary Cell Group” refers to the subset of serving cells including the PSCell and zero or more secondary cells for a UE configured with DC. The term “Serving Cell” refers to the primary cell for a UE in RRC_CONNECTED not configured with CA/DC there is only one serving cell including of the primary cell. The term “serving cell” or “serving cells” refers to the set of cells including the Special Cell(s) and all secondary cells for a UE in RRC_CONNECTED configured with CA. The term “Special Cell” refers to the PCell of the MCG or the PSCeIl of the SCG for DC operation; otherwise, the term “Special Cell” refers to the Pcell.

NFV Management and Orchestration (MANO Architecture)

FIG. 11 depicts an example management architecture 1100 of mobile networks that include virtualized network functions. The management architecture 1100 of FIG. 11 is a 3GPP management and ETSI NFV Management and Orchestration (MANO) architecture. The 3GPP management system 1154 of FIG. 11 is based on 4G networks, but aspects of the management system may be applicable to 5G networks.

The mobile network includes physical and virtualized network elements. Application-specific aspects of both Virtualized Network Functions (VNFs) and Physical Network Functions (PNFs), corresponding to physical network elements (NEs) 1152, are managed by the 3GPP management system.

In FIG. 11, the Itf-N 1102 is an interface between the Network Manager (NM) 1104 and the Domain Manager/Element Manager (DM/EM) 1106, the Os-Ma-nfvo 1108 is the reference point between the Operations Support System/Business Support System (OSS/BSS) 1110 (e.g., the NM) and the Network Functions Virtualization Orchestrator (NFVO) 1112, the Ve-Vnfm-em 1114 is the reference point between the EM and the Virtualized Network Function Manager (VNFM) 1116, and the Ve-Vnfm-vnf 1118 is the reference point between the Virtualized Network Function (VNF) 1120 and the VNFM 1116

The Network Functions Virtualization Infrastructure (NFVI) 1122 includes hardware and software components that together provide the infrastructure resources where VNFs are deployed. The infrastructure resources contain the hardware resources, virtualization layer software and the virtualized resources which the VNF relies on. NFVI resources under consideration are both virtualized and non-virtualized resources, supporting virtualized network functions and partially virtualized network functions.

Virtualized resources in-scope are those that can be associated with virtualization containers, and have been catalogued and offered for consumption through appropriately abstracted services, for example, compute including machines (e.g. hosts or bare metal), and virtual machines, as resources that comprise both CPU and memory; storage, including: volumes of storage at either block or file-system level; and network, including: networks, subnets, ports, addresses, links and forwarding rules, for the purpose of ensuring intra- and inter-VNF connectivity.

The NM 1104, which plays one of the roles of OSS/BSS and is the consumer of reference point Os-Ma-nfvo 1108. The NM 1104 provides the functions for the management of mobile network which includes virtualized network functions. The NM 1107 supports fault, configuration, accounting, performance, and security (FCAPS) management functions of the mobile network (e.g. IP Multimedia Subsystem [IMS], Evolved Packet Core [EPC]) and 3GPP service (e.g. data service, voice service) and supports the management of mobile network lifecycle. NM 1104 initiates the lifecycle management of European Telecommunications Standards Institute (ETSI)-defined Network Service (NS) and VNF, which are related to mobile network, through interaction with NFV-MANO 1150.

The EM and/or DM 1106 is responsible for FCAPS management functionality for a VNF 1120 on an application level and physical NE on a domain and element level. This mainly includes: fault management for VNF 1120 and physical NE; configuration management for VNF 1120 and physical NE; accounting management for VNF 1120 and physical NE; performance measurement and collection for VNF 1120 and physical NE; and security management for VNF 1120 and physical NE. EM/DM 1206 participates in lifecycle management functionality for a VNF 1120, such as by requesting a lifecycle management operation for a VNF 1220 to VNFM 1116, and exchanging information regarding the VNF 1120 and Virtualized Resources associated with the VNF 1120. The DM/EM 1106 (including EM extended functionality) can manage both PNF(s) and VNF(s).

The NFV-MANO 1150 includes an NFV Orchestrator (NFVO) 1112, VNF Manager (VNFM) 1116, and Virtualized Infrastructure Manager (VIM) 1124. The NFVO 1112 and VNFM 1116 share interfaces with the NM 1104, DM/EM 1106 and VNF 1120. The NFVO 1112 is responsible for the orchestration of NFVI 1122 resources across multiple VIMs, fulfilling the Resource Orchestration functions, and the lifecycle management of Network Services, fulfilling the Network Service Orchestration functions.

The management and orchestration of virtualized resources includes handing NFVI resources (e.g. in NFVI Nodes), in NFVI Points of Presence (NFVI-PoPs). Management of non-virtualized resources is restricted to provisioning connectivity to PNFs, necessary when a NS instance includes a PNF that needs to connect to a VNF, or when the NS instance is distributed across multiple NFVI-PoPs or N-PoPs.

The virtualized resources are leveraged for providing VNFs with the resources they need. Resource allocation in the NFVI 1122 is a potentially complex task because a lot of requirements and constraints may need to be met at the same time. Particularly requirements for network allocation add new complexity compared to known resource allocation strategies for computing resources in virtualized environments. For example, some VNFs 1120 require low latency or high bandwidth links to other communication endpoints.

Allocation and release of resources is a dynamic process, in response to consumption of those services by other functions. While the management and orchestrations function for virtualized infrastructure are VNF-unaware, resource allocations and releases may be needed throughout the VNF lifetime. An advantage of NFV is that with increasing load VNFs can dynamically consume services that allocate additional resource when scaling-out is triggered.

Services exposing virtualized resources include (non-exhaustive list): discovery of available services; management of virtualized resources availability/allocation/release; and virtualized resource fault/performance management.

In the case of virtualized resources distributed across multiple NFVI-PoPs, those services could either be exposed directly by the management and orchestration functions for each individual NFVI-PoP, or via a higher-level service abstraction presenting the virtualized resources across multiple NFVI-PoPs. Both types of services could be exposed to the consuming functions. In the case of the higher level service abstraction previously mentioned, the management and orchestration of virtualized resources and non-virtualized networking resources across those NFVI-PoPs falls under the responsibility of the management and orchestration of the virtualized infrastructure that may in turn use the services exposed directly by the management and orchestration functions of a single or across multiple NFVI-PoPs. In order to provide those services, the management and orchestration of the virtualized infrastructure consumes services provided by the NFVI.

The NFV management and orchestration functions that coordinate virtualized resources in a single NFVI-PoP and/or across multiple NFVI-PoPs need to ensure exposure of services that support accessing these resources in an open, well known abstracted manner. These services can be consumed by other authenticated and properly authorized NFV management and orchestration functions (e.g. functions that manage and orchestrate virtualized network functions).

Network Service Lifecycle management includes, inter alia, on-boarding Network Service, i.e. register a Network Service in the catalogue and ensure that all the templates describing the NS are on-boarded; instantiating Network Service, i.e. create a Network Service using the NS on-boarding artefacts; scaling Network Service, i.e. grow or reduce the capacity of the Network Service; updating Network Service by supporting Network Service configuration changes of various complexity such as changing inter-VNF connectivity or the constituent VNF instances. Performing create, delete, query, and update procedures for Virtualized Network Function Graph Descriptors (VNFFGs) associated to a Network Service; and terminating Network Services, i.e. request the termination of constituent VNF instances, request the release of NFVI resources associated to NSs, and return them to NFVI resource pool if applicable.

The deployment and operational behavior requirements of each Network Service is captured in a deployment template, and stored during the Network Service on-boarding process in a catalogue, for future selection for instantiation. The deployment template fully describes the attributes and requirements necessary to realize such a Network Service. Network Service Orchestration coordinates the lifecycle of VNFs that jointly realize a Network Service. This includes (not limited to) managing the associations between different VNFs, and when applicable between VNFs and PNFs, the topology of the Network Service, and the VNFFGs associated with the Network Service.

During the Network Service lifecycle, the Network Service Orchestration functions may monitor KPIs of a Network Service if such requirements were captured in the deployment template, and may report this information to support explicit request for such operations from other functions.

The Network Service Orchestration performs its services by using the VNF Management services and by orchestrating the NFV Infrastructure that supports the interconnection between VNFs functionality, and its functions are exposed in an open, well known abstracted manner as services to other functions. In order to fulfill its responsibilities, the Network Service Orchestration functions consume services exposed by other functions (e.g. Virtualized Infrastructure Management functions).

The services provided by Network Service Orchestration can be consumed by authenticated and properly authorized other functions (e.g. OSS, BSS).

The VNF Manager 1116 is responsible for the lifecycle management of VNF instances 1120. Each VNF 1120 instance is assumed to have an associated VNF Manager 1116. The VNF manager 1116 may be assigned the management of a single VNF instance, or the management of multiple VNF instances 1120 of the same type or of different types.

Most of the VNF Manager 1116 functions are assumed to be generic common functions applicable to any type of VNF. However, the NFV-MANO architectural framework needs to also support cases where VNF instances need specific functionality for their lifecycle management, and such functionality may be specified in the VNF Package.

The VNF 1120 is configured to perform VNF instantiation, including VNF configuration if required by the VNF deployment template (e.g. VNF initial configuration with IP addresses before completion of the VNF instantiation operation); VNF instantiation feasibility checking; VNF instance software update/upgrade; VNF instance modification; VNF instance scaling out/in and up/down; VNF instance-related collection of NFVI performance measurement results and faults/events information, and correlation to VNF instance-related events/faults; VNF instance assisted or automated healing; VNF instance termination; VNF lifecycle management change notification; management of the integrity of the VNF instance through its lifecycle; and overall coordination and adaptation role for configuration and event reporting between the VIM 1124 and the EM. The aforementioned functionalities may be exposed by means of interfaces and consumed by other NFV-MANO functional blocks or by authorized external entities:

The deployment and operational behavior of each VNF 1120 is captured in a template called Virtualized Network Function Descriptor (VNFD) that is stored in the VNF catalogue. NFV-MANO 1150 uses a VNFD to create instances of the VNF 1120 it represents, and to manage the lifecycle of those instances. A VNFD has a one-to-one correspondence with a VNF Package, and it fully describes the attributes and requirements necessary to realize such a VNF. NFVI resources are assigned to a VNF 1120 based on the requirements captured in the VNFD (containing resource allocation criteria, among others), but also taking into consideration specific requirements, constraints, and policies that have been pre-provisioned or are accompanying the request for instantiation and may override certain requirements in the VNFD (e.g. operator policies, geo-location placement, affinity/anti-affinity rules, local regulations).

The information elements to be handled by the NFV-MANO 1150, including the VNFD among others, need to guarantee the flexible deployment and portability of VNF instances on multi-vendor and diverse NFVI environments, e.g. with diverse computing resource generations, diverse virtual network technologies, etc. To achieve this, hardware resources need to be properly abstracted and the VNF requirements be described in terms of such abstraction.

The VNFM 1116 has access to a repository of available VNF Packages and different versions of them, all represented via their associated VNFDs. Different versions of a VNF Package may correspond to different implementations of the same function, different versions to run in different execution environments (e.g. on different hypervisors, dependent on NFVI resources availability information, etc.), or different release versions of the same software. The repository may be maintained by the NFVO or another external entity.

The Virtualized Infrastructure Manager (VIM) 1124 is responsible for controlling and managing the NFVI compute, storage and network resources, usually within one operator's Infrastructure Domain (e.g. all resources within an NFVI-PoP, resources across multiple NFVI-POPs, or a subset of resources within an NFVI-PoP) as discussed previously. A VIM 1124 may be specialized in handling a certain type of NFVI resource (e.g. compute-only, storage-only, networking-only), or may be capable of managing multiple types of NFVI resources (e.g. in NFVI-Nodes).

The southbound interfaces interface with a variety of hypervisors and Network Controllers in order to perform the functionality exposed through its northbound interfaces. Other VIM implementations may directly expose the interfaces exposed by such compute, storage, Network Controllers as specialized VIMs. A particular example of a specialized VIM is a WAN Infrastructure Manager (WIM), typically used to establish connectivity between PNF endpoints in different NFVI-PoPs. The VIM implementation is out of scope for NFV-MANO; however the interfaces exposed by VIMs are in-scope.

The VIM 1124 is configured to orchestrate the allocation/upgrade/release/reclamation of NFVI resources(including the optimization of such resources usage), and manage the association of the virtualized resources to the physical compute, storage, networking resources, where the VIM 1124 keeps an inventory of the allocation of virtual resources to physical resources, e.g. to a server pool and/or the like.

The VIM 1124 is also configured to support the management of VNF Forwarding Graphs (create, query, update, delete), e.g. by creating and maintaining Virtual Links, virtual networks, sub-nets, and ports, as well as the management of security group policies to ensure network/traffic access control.

The VIM 1124 is also configured to manage, in a repository, inventory related information of NFVI hardware resources (compute, storage, networking) and software resources (e.g. hypervisors), and discovery of the capabilities and features (e.g. related to usage optimization) of such resources; manage the virtualized resource capacity (e.g. density of virtualized resources to physical resources), and forwarding of information related to NFVI resources capacity and usage reporting; manage software images (add, delete, update, query, copy) as requested by other NFV-MANO functional blocks (e.g. NFVO 1112). The VIM 1124 maintains repositories for software images, in order to streamline the allocation of virtualized computing resources, and a validation step, performed by VIM 1124, is required for software images before storing the image (e.g. VNF package on-boarding and update). Image validation operations during run-time, e.g. during instantiation or scaling, are outside the scope of the current version of the present document.

The VIM 1124 is also configured to collect performance and fault information (e.g. via notifications) of hardware resources (compute, storage, and networking) software resources (e.g. hypervisors), and virtualized resources (e.g. VMs); and forwarding of performance measurement results and faults/events information relative to virtualized resources.

The VIM 1124 is also configured to manage catalogues of virtualized resources that can be consumed from the NFVI 1122. The elements in the catalogue may be in the form of virtualized resource configurations (virtual CPU configurations, types of network connectivity (e.g. L2, L3), etc.), and/or templates (e.g. a virtual machine with 2 virtual CPUs and 2 GB of virtual memory).

FIG. 12 depicts another example of a management services architecture 1200. The management services (e.g., NF instantiation services) may be named differently than as shown by FIGS. 11 and 12, as the name of the management services are not the focus of the present embodiments. The present disclosure is related to the functionality of the management services.

In the examples of FIGS. 11 and 12, the NF instantiation service producer 1202 may provide a management service to a consumer, by receiving a request from a consumer to instantiate a 3GPP NF; checking whether the VNF package(s) of the VNF(s) realizing the virtualized part of the 3GPP NF have been on-boarded to the NFV MANO system, and on-boarding the VNF package(s) that have not been on-boarded yet; interacting with the NFV MANO system to instantiate the VNF(s) that are realizing the virtualized part of subject 3GPP NF; informing the consumer that the 3GPP NF has been instantiated; and creating the Managed Object Instances (MOIs) for the subject 3GPP NF.

The NF configuration service producer 1204 may provide management services to a consumer, by receiving a request from a consumer to configure a 3GPP NF instance; configuring the 3GPP NF instance; and informing the consumer that the 3GPP NF instance has been configured. The request from the consumer to configure a 3GPP NF instance may include a request to create the MOI(s) for the 3GPP NF. The request from the consumer to configure the 3GPP NF instance may be a MOI attribute modification request. Configuring the 3GPP NF instance may include interaction with the ETSI NFV MANO system to update the corresponding VNF instance(s) realizing the virtualized part of the 3GPP NF.

The network creation service producer 1206 may provide management services to a consumer, by receiving a request from a consumer to create a 3GPP network; preparing the NSD(s) for the NS(s) that are to realize the requested 3GPP network, and on-boarding the NSD(s) to ETSI NFV MANO system; on-boarding the VNF package(s) of the constituent VNFs to ETSI NFV MANO system, if the VNF package has not yet been on-boarded; interacting with ETSI NFV MANO system to instantiate the NS(s); consuming a management service to configure the 3GPP NF instance(s) that are constituting the subject 3GPP network; and creating the MOI(s) for the created network. The interaction with the ETSI NFV MANO system to instantiate the NS(s) may include the instantiation of constitute (constituent VNFs). The ETSI NFV MANO system may inform the management service producer about the instantiation of VNFs. The management service producer may create the MOI(s) for the newly instantiated VNFs, and may provide the NF configuration service. Additionally, the management service being consumed to configure the 3GPP NF instance(s) may be the NF configuration service.

The network configuration service producer 1208 may provide management services to a consumer, by receiving a request from a consumer to configure a 3GPP network; configuring the 3GPP network; and informing the consumer that the 3GPP network has been configured. The request from the consumer to configure a 3GPP network includes a request to create the MOI(s) for the 3GPP network, and the request from the consumer to configure a 3GPP network is a MOI attribute modification request. Configuring the 3GPP network further may include interaction with the ETSI NFV MANO system to update the corresponding NS instance(s) realizing (fully or partially) the 3GPP network. The interaction with the ETSI NFV MANO system to update the NS(s) may include the instantiation of new VNFs. The ETSI NFV MANO system may inform a management service producer about the instantiation of VNFs. The management service producer may create the MOI(s) for the newly instantiated VNFs, and the management service producer may provide the NF configuration service. In addition, configuring the 3GPP network further includes configuring the 3GPP NFs, and configuring the 3GPP NFs may be via consuming the management service for NF configuration.

The NSSI creation service producer (NSSMF) 1210 may create a NSSI for a consumer, by consuming a management service to configure the 3GPP network; and/or consuming a management service to configure the 3GPP NF(s). The management service consumed to configure the 3GPP network may be a network configuration service, and the management service consumed to configure the 3GPP NF(s) may be an NF configuration service.

Management Services

5G management is based on Service Based Architecture (SBA) where each management function is a producer that produces management services to be consumed by other management functions. FIG. 13 shows an example of 5G management services. A management service offers management capabilities. These management capabilities are accessed by management service consumers via standardized service interface composed of individually specified management service components.

In FIG. 13, the Network Function Management Function (NFMF) 1302 provides NF management services to Network Slice Subnet Management Function (NSSMF); the NSSMF 1210 consumes NF management services to provide NSS management services to Network Slice Management Function (NSMF) 1212; and the NSMF 1212 consumes NSSMF management services to provide NS management services to other management entity.

A management service offers management capabilities. These management capabilities are accessed by management service consumers via standardized service interface composed of individually specified management service components. An example is shown by FIG. 14A.

A management service 1400 may include a management service component type A and management service component type B; a management service component type A, management service component type B, and management service component type C; or any combination of management component types A, B, and/or C. An example of management service 1400 and related management service component type A, type B and type C is shown by FIG. 14B.

Management Service Components

A management service 1400 combines elements of management service component type A, B and C. The management service components are combined to allow a management service consumer to interact with a management service producer via a specified service interface.

Management service component type A is a group of management operations and/or notifications agnostic of managed entities.

Management service component type B is the management information represented by information model of managed entities.

Management service component type B includes the following models:

1) Network resource model for NG-RAN and NR (e.g., as defined in 3GPP Technical Specification (TS) 28.541). 2) Network resource model for 5GC (e.g., as defined in 3GPP TS 28.543). 3) Network slice information model (e.g., as defined in 3GPP TS 28.532). 4) Network slice subnet information model (e.g., as defined in 3GPP TS 28.532).

In embodiments, additional other models belong to type B is to be added later.

Management service component type C is performance information of the managed entity and fault information of the managed entity.

Management service component type C includes the following information:

1) Alarm information (e.g., as defined in 3GPP TS 28.546). 2) Performance data (e.g., as defined in 3GPP TS 28.552, 28.553, 28.554, and 32.425).

In embodiments, management service component type C could be merged with Management service component type B. Mechanisms for collecting Minimization Drive Test (MDT) data may also be included. Additionally, more management information belonging to type C is to be added later.

Management capability exposure governance provides exposure governance on basic elements of management function service based interface:

1) Management service component type A 2) Management service component type B 3) Management service component type C

As shown by FIG. 15, when there is a Management Service A exposure without exposure governance, Management Service A′ Consumer can access all management capability offered by Management Service A′ Producer. When Management Service A is exposed with applied exposure governance it becomes Management Service A′. Management Service A′ Consumer can access Management Service A′ after following steps:

1) Management Service A, exposed by Management Service A′ Producer, is consumed by Management Service A′ Consumer; 2) Management Service B, exposed by Management Service B Producer, is consumed by Operator who applies exposure governance on exposed Management Service A 3) Management Service A′ Producer produces Management Service A 4) The Management Service A′ Consumer, that consumes Management Service A, the Management Service B and Management Service A′ Producer, that produces Management Service B (with management capability exposure governance) and Management Service A, can be represented as one management function entity (e.g., EGMF).

Referring to FIG. 16A, the Management Function (MF) 1600 is a management entity whose externally-observable behavior and interfaces are specified by 3GPP. In the service-based management architecture, MF 1600 plays the role of either Management Service producer or Management Service consumer. A Management Service produced by MF 1600 may have multiple consumers. The MF 1600 may consume multiple Management Services from one or multiple Management Service producers. An example of an MF 1600 playing both roles (Management Service producer and consumer) is illustrated by FIG. 16A.

Management Functions 1600 may interact by consuming Management Services produced by other Management Functions. FIG. 16B illustrates multiple scenarios, including: MF1 produces Management Service MnS-a; MF2 consumes Management Service MnS-a produced by MF1 and produces Management Services MnS-b and MnS-c; MF3 produces Management Service MnS-c; MF4 consumes Management Service MnS-b produced by the MF2; and MF5 consumes Management Services MnS-c produced by the MF2 and MF3, and in turn produces the same Management Service MnS-c. The behaviour of MF5 may be seen as aggregation of Management Services MnS-c.

Mobile networks have the capability to support a variety of services, increasing flexibility of the network may cause management challenges. The management system can benefit from management data analytics services to make the mobile network more efficient in responding to various requests. The management data analytics utilize the network management data collected from the network and make the corresponding analytics based on the collected information. For example, the information provided by PM data analytics services can be used to optimize network performance, and the information provided by FM data analytics services can be used to predict and prevent failures of the network. For mobile networks with slicing, a network slice data analytics service can consume performance measurements and fault measurements data for its constituent network slice subnets.

FIG. 17 shows an example service based architecture 1700 for management data analytics.

The Management Data Analytics Service (MDAS) can be used for NF(s), NSSI(s), NSI(s) and Subnetwork(s)/network(s). The MDAS comprises an MDAS producer that analyzes management data (e.g., performance measurements, alarm information, and configuration information, etc.) of the NF(s), NSSI(s), NSI(s) and Subnetwork(s)/network(s) and provides management data analytical KPIs. An example of such an MIDAS 1800 is shown in FIG. 18.

FIG. 19 shows an example of an MDAS 1900 being provided by a Management Data Analytics Function (MDAF), which is/are consumed by other management functions. The management services for a mobile network including network slicing may be produced by a set of functional blocks. This annex shows an example of such deployment scenario where functional blocks (such as NSMF, NSSMF, NFMF and CSMF) are producing and consuming various management services.

In this deployment example the NFMF (Network Function Management Function) provides the management services for one or more NF and may consume some management services produced by other functional blocks. The NF provides some management services, for example the NF performance management services, NF configuration management services and NF fault supervision services. NSSMF provides the management services for one or more NSSI and may consume some management services produced by other functional blocks. NSMF provides the management services for one or more NSI and may consume some management services produced by other functional blocks. The MDAF provides the Management Data Analytics Service for one or more NF, NSSI and/or NSI, and may consume some management services produced by other functional blocks, and the CSMF consumes the management service(s) provided by the other functional blocks. This deployment example does not illustrate what management services the CSMF consumes. In this example, one functional block may consume the management service(s) provided by another functional block, depending on the management scope of the functional block(s). The scope may be expressed in the terms of Management Service Components (see e.g., section 2 supra).

However, the concrete management data analytical KPIs have not been defined yet. Embodiments herein define the management data analytical KPIs for prediction of traffic volume, resource utilization tendency, and indication of the RAN condition(s). The Management Data Analytics Service is relied on big data technologies and is one essential step of adopting AI (Artificial Intelligence) in telecommunications.

MDAS can be deployed at different levels, for example, at domain level (e.g., RAN, CN, NSSI) or in a centralized manner (e.g., in a PLMN level). A domain-level MDAS provides domain specific analytics, e.g., resource usage prediction in a CN or failure prediction in a NSSI, etc. A centralized MDAS can provide end-to-end or cross-domain analytics service, e.g., resource usage or failure prediction in an NSI, optimal CN node placement for ensuring lowest latency in the connected RAN, etc.

FIG. 20 illustrates an example deployment model of the MDAS. In the example shown in FIG. 20, the Domain MDAF 2002 produces domain MDAS. The domain MDAS is consumed by the Centralized MDAF 2004 and other authorized MDAS Consumers 2006 (for example, infrastructure manager, network manager, slice manager, slice subnet manger, other third party OSS, etc.). The Centralized MDAF 2004 produces centralized MDAS, which is consumed by different authorized MDAS Consumers 2006.

Example Systems and Methods for Transmitting Performance Data

FIGS. 21 and 22 show example embodiments for transmitting performance data regarding a wireless communications network. One or more of the described embodiments can be used in accordance with 3rd Generation Partnership Project (3GPP) technical specifications (TS), such as (but not limited to) 3GPP TS 28.550, 3GPP TS 28.552, 3GPP TS 28.554, 3GPP TS 28.622, 3GPP TS 32.158, and 3GPP TS 32.425 (the contents of which are incorporated by reference in their entirety).

In an example implementation, a management service (MnS) producer can monitor the performance of a wireless communications network, and generate performance data based on the monitoring. As an example, the performance data can include information such as the latency associated with the wireless communications network, the throughput associated with the wireless communications network, a number of registered subscribers for the wireless communications network, a number of attempts to perform a particular operation with response to the wireless communications network, and/or any other type of information regarding the wireless communications network.

Further, the MnS producer can transmit at least some of the generated performance data to one or more MnS consumers. In some implementations, the performance data can be streamed to the one or more MnS consumers using a protocol that provides for full-duplex (e.g., two-way) communications channels, such as WebSocket, rather than a protocol that only provides for half-duplex (e.g., one-way) communications channels, such as Hypertext Transfer Protocol (HTTP).

In some implementations, the MnS producer can also make at least some of the performance data available for retrieval on demand, and report the availability to one or more management service consumers (e.g., by generating and transmitting one or more notifications to the one or more management service consumers). In response, the one or more MnS consumers can initiate the retrieval of some or all of the available performance data from the MnS producer.

In some implementations, the MnS producer can also transmit notifications to one or more MnS consumers when the performance of the wireless communications network satisfies certain conditions (e.g., if one or more performance metrics of the wireless communications network crosses a particular threshold value, if a particular event occurred with respect to the wireless communications network, etc.). Accordingly, the MnS consumers can be quickly notified of any changes to the condition of the wireless communications network, and in response, can perform one or more appropriate remedial actions in a timely manner.

An example process 1200 for transmitting performance data regarding a wireless communications network is shown in FIG. 21. The process 2100 can be performed at least in part, using one or more of the network functions, components, and/or systems shown in FIGS. 1-20. As an example, the process 1200 can be performed by a MnS producer 2102 (e.g., one or more network functions, components, and/or systems that generate data regarding one or more aspects of a wireless communications module and/or provide other services) to transmit performance data to an MnS consumer 2104 (e.g., one or more network functions, components, and/or systems that receive or “consume” data regarding the wireless communications module and/or consume other services). In some implementations, the MnS producer 2102 and/or the MnS consumer 2204 can be implemented as described above with respect to FIGS. 11-20. Further, in some implementations, the wireless communications network can be a 5G network in accordance with 3GPP technical standards.

According to the process 2100, the MnS producer 2102 transmits a request to establish a connection for streaming performance data to the MnS consumer 2104 (step 2106).

In response, the MnS consumer establishes the connection, and transmits a confirmation that the connection has been established to the MnS producer (2108).

In some implementations, the first request and/or the first response can include a HTTP GET command. The GET command can include an indication to upgrade the connection from an HTTP connection to a WebSocket connection. This can be beneficial, for example, in providing backwards compatibility with systems that can communicate according to HTTP, but cannot communicate according to the WebSocket protocol.

In some implementations, the first request and/or the first response can be used to realize the “Stage 2” operation “establishStreamingConnection,” as defined 3GPP TS 28.550.

In some implementations, the connection can be established according to a protocol that provides for full-duplex (e.g., two-way) communications channels, such as WebSocket. WebSocket is a computer communications protocol that provides full-duplex communication channels over a single Transmission Control Protocol (TCP) connection. The WebSocket protocol was standardized by the Internet Engineering Task Force (IETF) as RFC 6455 (the contents of which are incorporated by reference in its entirety).

The use of the WebSocket protocol over other protocols (e.g., HTTP) can provide various technical benefits. For example, the WebSocket protocol enables interaction between a client application (e.g., a web browser) and a web server with lower overhead than half-duplex alternatives such as HTTP polling. Accordingly, data can be transferred in real-time (or substantially real-time) from and to the server. This is made possible by providing a standardized protocol for the server to transmit content to the client without being first requested by the client, and allowing messages to be transmitted back and forth while keeping the connection open. Accordingly, a two-way ongoing “conversation” can take place between the client and the server. In some implementations, the communications can be performed over TCP port number 80 (or 443 in the case of Transport Layer Security (TLS)-encrypted connections).

Once the connection has been established, the MnS producer 2102 streams one or more units of performance data to the MnS consumer 2104 using the connection (step 2110). Each unit of performance data can include one or more performance metrics regarding the wireless communications network.

As examples, the performance metrics can include a latency associated with at least a portion of the wireless communications network, a throughput associated with at least the portion of the wireless communications network, a number of registered subscribers for at least the portion of the wireless communications network, a number of established network sessions for at least the portion of the wireless communications network, and/or an energy efficiency of at least the portion of the wireless communications network. As further examples, performance metrics can include a number of attempts to perform a particular operation with respect to at least a portion of the wireless communications network, a number of successful attempts to perform the particular operation with respect to at least the portion of the wireless communications network, and/or a number of unsuccessful attempts to perform the particular operation with respect to at least a portion of the wireless communications network. Other example performance metrics are described in 3GPP TS, 3GPP TS 28.552, 3GPP TS 28.554, and 3GPP TS 32.425, the contents of which are incorporated by reference in their entirety.

In some implementations, the data contained with the stream (e.g., each unit of performance data) can be defined in a “streamInfoList” parameter of an “establishStreamingConnection operation.” This information can be encapsulated in the Query part of the Request-Line of the HTTP GET operation. In some implmetnations, this information can be encoded according to Abstract Syntax Notation One (ASN. 1).

The MnS producer 2102 can continue to stream units of performance data to the MnS consumer 2104 over a period of time. For example, the MnS producer 2102 can transmit multiple units of performance data to the MnS consumer 2104 continuously, periodically, or according to some other pattern over the period of time, without closing the connection between transmissions.

In some implementations, streaming units of performance data can include sending one of more WebSocket Data frames sequentially to the first MnS consumer. Each WebSocket Data frame can include one or more units of performance data (e.g., in the payload data of the WebSocket Data frame). In some implementations, the payload data can be encoded according to ASN. 1. In some implementations, each WebSocket Data frame can have an opcode of 0x2.

In some implementations, the streaming of performance data can be used to realize the “Stage 2” operation “reportStreamData,” as defined 3GPP TS 28.550.

After the MnS producer 2102 has completed streaming performance data to the MnS consumer 2104, the MnS producer 2102 transmits a request to terminate the connection to the MnS consumer 2104 (step 2112).

In response, the MnS consumer 2104 terminates the connection, and transmits a confirmation that the connection has been terminated to the MnS producer 2102 (step 2114).

In some implementations, the second request and/or the second response can include a WebSocket Close frame. In some implementations, the WebSocket Data frame can have an opcode of 0x8.

In some implementations, the second request and/or the second response can be used to realize the “Stage 2” operation “terminateStreamingConnection,” as defined 3GPP TS 28.550.

In some implementations, the MnS consumer can subscribe to notifications from the MnS producer. For example, the MnS consumer can request that the MnS producer transmit certain types of performance data (e.g., certain types of data offered by a performance data file reporting service of the MnS producer). Accordingly, the MnS consumer can selectively obtain performance data regarding the wireless communications network.

For instance, the MnS producer can receive a subscription request from a second MnS consumer. In response, the MnS producer can transmit one or more notifications to the second MnS consumer according to the subscription request. Each notification can include one or more second performance metrics regarding the wireless communications network (e.g., one or more second performance metrics specified by the subsequent request). In some implementations, the second performance metrics can be transmitted as one or more data files. In some implementations, each notification can include a “notifyFileReady” message or a “notifyFilePreparationError” message, as defined in 3GPP TS 28.532.

As another example, the MnS consumer can request that the MnS producer notify the MnS consumer when the performance of the wireless communications network satisfies certain conditions (e.g., as a part of a performance threshold monitoring service or the MnS producer). Accordingly, the MnS consumers can be quickly notified of any changes to the condition of the wireless communications network, and in response, can perform one or more appropriate remedial actions in a timely manner. For instance, the MnS producer can receive a subscription request from a second MnS consumer. In response, the MnS producer can transmit one or more notifications to the second MnS consumer according to the subscription request. The subscription request can include an indication of a threshold value with respect to the one more second performance metrics, and the one or more notifications can be transmitted responsive to the one more second performance metrics crossing the threshold value. In some implantations, each notification can include a “notifyThresholdCrossing” message, as defined in 3GPP TS 28.532.

In some implementations, the MnS consumer can also transmit a request to the MnS producer to list each of the performance data files (e.g., containing one or more performances metrics) that are available for retrieval. In response, the MnS producer can transmit the requested list to the MnS consumer. The request and response can be performed, for example, one or more HTTP operations.

In some implementations, the HTTP operation can be a HTTP GET command, and can be used to realize the “Stage 2” operation “listAvailableFiles,” as defined in 3GPP TS 28.532. For example, the request can include input parameters such as “managementDataType” (e.g., indicating the type of performance data that is requested), “beginTime” (e.g., indicating the beginning of the time period for which performance data is requested), and “endTime” (e.g., indicating the end of the time period for which performance data is requested). These inputs can be encapsulated in the Query part of the Request-Line of the HTTP GET command. Further, the request can include an output parameter “fileInfoList” (e.g., listing the available performance data files). This parameter can be encapsulated in the response body of the Request-Line of the HTTP GET operation.

Example Performance Data Streaning Operations Example Mapping of Commands Between a “Server Sent” Protocol and an “In-Sync” Protocol:

In some implementations, performance data transmission operations that were previously performed using a half-duplex communications channel (e.g., according to “server sent” protocol, such as HTTP) can be instead performed using a full-duplex communications channel (e.g., according to an “in-sync” (IS) protocol, such as WebSocket). Example mappings of SS commands to IS commands are detailed below.

In some implementations, the “Stage 3” solution set for performance data streaming related operations (as defined in clause 6.2 of TS 28.550) using on WebSocket protocol can be defined as follows.

The IS operations can be mapped to SS equivalents according to Table 1.

TABLE 1 Mapping of IS operations to SS equivalents. IS operation WebSocket Method/frame Qualifier establishStreamingConnection HTTP GET (Upgrade) M terminateStreamingConnection Close frame sent M (frame with opcode of 0 × 8), and Close frame received (frame with opcode of 0 × 8) reportitreamData Data frame sent M (frame with opcode of 0 × 2)

For the operation “establishStreamingConnection,” the IS operation parameters can be mapped to SS equivalents according to Tables 3 and 4.

TABLE 2 Mapping of IS operation input parameters to SS equivalents (HTTP GET request-Upgrade request). IS operation SS SS SS parameter parameter parameter parameter name location name type Qualifier producerReference n/a — n/a n/a streamInfoList Request-Line Query String (see Note 1), and M the scheme of Query component is specified in clause 9.3.1. — Request-Line Method Constant string: GET M Request-URI String (see Note 1) HTTP-Version String (see Note 2) — Headers Host String (see Note 3) — Headers Upgrade Constant string: M websocket — Headers Connection Constant string: Upgrade M — Headers Sec-WebSocket-Key string — Headers Sec-WebSocket-Version string NOTE 1: The Request-URI shall follow the format of wss-URI as defined in IETF RFC 6455, and the Request-URI shall contain the query component which is mapped from the stage 2 streamInfoList parameter. NOTE 2: The HTTP version shall be not earlier than HTTP/1.1. NOTE 3: The Host header indicates the Internet host of the stream target. NOTE 4: Other SS parameters (not listed in this table) independent from the Stage 2 may be used, according to the WebSocket protocol (see IETF RFC 6455).

TABLE 3 Mapping of IS operation output parameters to SS equivalents (HTTP GET response - Upgrade response). IS operation SS SS SS parameter parameter parameter parameter name location name type Qualifier connectionId n/a — n/a n/a status Status- HTTP-Version String (see Note 1) M Line Status-Code String (see Note 2) Reason-Phrase String (see Note 2) — Headers Upgrade Constant string: M websocket — Headers Connection Constant string: M Upgrade Headers Sec- String M WebSocket- Accept NOTE 1: The HTTP version shall be not earlier than HTTP/1.1. NOTE 2: The valid values of Status-Code and Reason-Phrase are as following: for a successful operation: the Status-Code is “101” and Reason-Phrase “Switching Protocols”; for a failed operation with the reason “unexpectedStreams”, the Status-Code is “490” and Reason-Phrase is “unexpectedStreams”; for a failed operation with other reasons, the Status-Code and Reason-Phrase are assigned according to IETF RFC 2616. NOTE 3: Other SS parameters (not listed in this table) independent from the Stage 2 may be used, according to the WebSocket protocol (see IETF RFC 6455).

For the operation “terminateStreamingConnecdion,” the IS operation parameters can be mapped to SS equivalents according to Tables 4 and 5.

TABLE 4 Mapping of IS operation input parameters to SS equivalents (WebSocket Close frame sent). IS operation SS SS SS parameter parameter parameter parameter name location name type Qualifier connectionId n/a — n/a n/a — Opcode (see — Constant value: M clause 5 of 0x8 IETF RFC 6455)

TABLE 5 Mapping of IS operation output parameters to SS equivalents (Web Socket Close frame received). IS operation SS SS SS parameter parameter parameter parameter name location name type Qualifier Status Opcode — For a successful M operation, the Opcode is 0 × 8, and for an unsuccessful operation, the Opcode has a value other than 0 × 8 (see clause 5 of IETF RFC 6455).

For the operation “reportStreamData,” the IS operation parameters can be mapped to SS equivalents according to Tables 6 and 7.

TABLE 6 Mapping of IS operation input parameters to SS equivalents (WebSocket Data frame sent with Opcode of 0x1). IS operation SS SS SS parameter parameter parameter parameter name location name type Qualifier streamId Payload streamId See clause 9.3.2 M data for the ASN.1 of Performance Data Stream Units. granularityPe- Payload granularityPe- See clause 9.3.2 M riodEndTime data riodEndTime for the ASN.1 of Performance Data Stream Units. measResults Payload measResults See clause 9.3.2 M data for the ASN.1 of Performance Data Stream Units.

TABLE 7 Mapping of IS operation output parameters to SS equivalents. IS operation SS SS SS parameter parameter parameter parameter name location name type Qualifier Status n/a — n/a n/a See Note 1. NOTE 1: The delivery of WebSocket Data frame is taken care of by the underlying TCP (see IETF RFC 793 [t]) which provides reliable data transmission and ensures the data delivery. There is no mechanism at WebSocket protocol level to report the delivery status for WebSocket Data frame.

Examples Schemes of a WebSocket-Based Solution Set Example Scheme of Query Component of Request-Line:

This section specifies an example scheme for the Query component of the Request-Line of HTTP GET operation (HTTP Upgrade) for WebSocket protocol as the SS of performance data streaming.

The Query component is mapped from the stage 2 stage 2 streamInfoList parameter. The scheme uses the ABNF syntax defined in IETF RFC 5234, based on the terminology and ABNF productions defined by the URI specification in IETF RFC 3986.

The scheme of Query component for WebSocket-based SS is as follows:

Query = streaminfo [ * (“&” streamInfo) ] streamInfo = “streamId=” streamId “;” “measObj=” measObjURL “;” “measTypes=” measTypeList streamId = * (ALPHA / DIGIT)   ; see ALPHD and DIGIT in IETF RFC 3986 measOblURI =*(pchar)  ; see pchar in IETF RFC 3986, and ; the measObjURL is the URL mapped from ; the DN of the measured object instance ; according to the mapping rule defined ; in TS 32.158. measTypeList = measType [ * (“,” measType) ] measType = * (ALPHA / DIGIT / “.”)   ; the measType is the measurement name ; defined in the performance measurements ; specifications, such as TS 28.552.

Example ASN.1 Definition for Performance Data Stream Units as Payload Data

For performance data streaming, the type of WebSocket Data frame can be binary (with opcode of 0x2).

This section specifies an example Abstract Syntax Notation One (ASN.1) definition for the Performance Data Stream Units as Payload data of a WebSocket Data frame.

The Performance Data Stream Units are described using ASN.1 as specified in ITU-T Rec. X.680 and X.681. Transfer syntax for Performance Data Stream Units is derived from their ASN.1 definitions by use of Packed Encoding Rules (PER), unaligned as specified in ITU-T Rec. X.691.

The following encoding rules apply in addition to what has been specified in ITU-T Rec. X.691:

-   -   When a bit string value is placed in a bit-field as specified in         clause 15.6 to 15.11 in ITU-T Rec X.691, the leading bit of the         bit string value shall be placed in the leading bit of the         bit-field, and the trailing bit of the bit string value shall be         placed in the trailing bit of the bit-field;     -   When decoding a BIT STRING or OCTET STRING constrained with a         Contents Constraint, PER decoders are required to never report         an error if there are extraneous zero or non-zero bits at the         end of the BIT STRING or OCTET STRING.     -   NOTE: The terms “leading bit” and “trailing bit” are defined in         ITU-T Rec. X.680. When using the “bstring” notation, the leading         bit of the bit string value is on the left, and the trailing bit         of the bit string value is on the right.

The ASN.1 definition of Performance Data Stream Units as Payload data of WebSocket Data frame can be as follows:

X -- ASN1START -- PDSUs-START PDSUs : := SEQUENCE OF PDSU PDSU : := SEQUENCE { streamId OCTET STRING, granularityPeriodEndTime OCTET STRING, measResults SEQUENCE OF measValue } measValue : := OCTET STRING -- PDSUs-STOP ASN1STOP

Example Performance Data File Reporting Service Mapping of Commands Between a “Server Sent” Protocol and an “In-Sync” Protocol:

In some implementations, performance data file reporting service operations that were previously performed using a half-duplex communications channel (e.g., according to “server sent” protocol, such as HTTP) can be instead performed using a full-duplex communications channel (e.g., according to an “in-sync”(IS) protocol, such as WebSocket). Example mappings of SS commands to IS commands are detailed below.

The IS operations can mapped to SS equivalents according to Table 8.

TABLE 8 Mapping of IS operations to SS equivalents. HTTP IS operation Method Resource URI Qualifier listAvailableFiles GET /availFiles M subscribe POST /subscriptions M unsubscribe DELETE /subscriptions M DELETE /subscriptions/{subscriptionId} M

For the operation “listAvailableFiles,” tThe IS operation parameters can be mapped to SS equivalents according to Tables 9 and 10.

TABLE 9 Mapping of IS operation input parameters to SS equivalents (HTTP GET). IS operation SS SS SS parameter parameter parameter parameter name location name type Qualifier manage- query manage- manage- M mentDataType mentDataType mentDataType- Type beginTime query beginTime dateTime-Type M endTime query endTime dateTime-Type M

TABLE 10 Mapping of IS operation output parameters to SS equivalents (HTTP GET). IS operation SS SS SS parameter parameter parameter parameter name location name type Qualifier fileInfoList response body n/a fileInfoRetrieval- M ResponseType Status response status n/a n/a M codes error error-ResponseType response body

For the operations “subscribe” “unsubscribe,” the operations notifyFileReady and notifyFilePreparationError can be performed, as described below.

The IS notifications can be mapped to SS equivalents according to Tables 11 and 12.

TABLE 11 Mapping of IS notifications to SS equivalents. HTTP IS notifications Method Resource URI SQ notifyFileReady POST /notificationSink M notifyFilePreparationError POST /notificationSink M

TABLE 12 Mapping of IS notification input parameters to SS equivalents (HTTP POST). IS operation SS SS SS parameter parameter parameter parameter name location name type SQ objectClass request href uri-Type M objectInstance body notificationId request notificationId notificationId- M body Type eventTime request eventTime dateTime-Type M body notificationType request notificationType notificationType- M body Type fileInfoList request fileInfoList array(fileInfo- M body Type) additionalText request additionalText additionalText- O body Type

For the operation “notifyFilePreparationError,” the IS notification parameters can be mapped to SS equivalents according to Table 13.

TABLE 13 Mapping of IS notification input parameters to SS equivalents (HTTP POST). IS operation SS SS SS parameter parameter parameter parameter name location name type SQ objectClass request href uri-Type M objectInstance body notificationId request notificationId notificationId- M body Type eventTime request eventTime dateTime-Type M body notificationType request notificationType notificationType- M body Type fileInfoList request fileInfoList array(fileInfo- M body Type) reason request reason reason-Type O body additionalText request additionalText additionalText- O body Type

Example Resource Structure

FIG. 22 shows an example resource structure 2200 of the performance data file reporting service.

Table 14 shows an overview of the resources and applicable HTTP methods.

TABLE 14 Resources and methods overview. Resource Resource HTTP name URI Method Description availFiles /availFiles GET Retrieve the information of the available files subscriptions /subscriptions POST Create a subscription subscriptions /subscriptions DELETE Delete all subscriptions made with a consumerReferenceId subscription /subscriptions/ DELETE Delete a single {subscriptionId} subscription notificationSink /notificationSink POST Send notifications

Example Resource Definitions

Resource “/availFiles”:

This resource represents the information about a collection of available files.

The Uniform Resource Identifier (URI) can be defined as follows: Resource URI=

{DN_prefix_authority_part}/{DN_prefix_remainder}/PerfDataFileReportMnS/v1530/availFiles

Table 15 shows an example definition of resource URI variables.

TABLE 15 URI variables. Name Definition DN_prefix_authority_part See subclause 4.4 of TS 32.158 DN_prefix_ remainder See subclause 4.4 of TS 32.158

Http Methods:

HTTP GET can support the URI query parameters specified in Table 16.

TABLE 16 URI query parameters supported by the GET method on this resource Name Data Type Description SQ manage- manage- To filter the available files based M mentDataType mentDataType on the management data type. beginTime dateTime-Type To filter the available files who M became ready no later than this time stamp. endTime dateTime-Type To filter the available files who M became ready no earlier than this time stamp.

This method can support the request data structures, the response data structures and response codes specified in Table 17.

TABLE 17 Data structures supported by the GET response body on this resource. Response Data type codes Description SQ fileInfoRetrieval- 200 OK The resource representation of M ResponseType the infomraiton about the available files retrieved. error-ResponseType 4xx/5xx Returned in case of an error M Resource “/subscriptions”:

This resource is a container resource for individual subscriptions.

The URI can be defined as follows:

Resource URI:

{DN_prefix_authority_part}/{DN_prefix_remainder}/PerfDataFileReportMnS/v1530/subscriptions

Http Methods:

HTTP POST can support the URI query parameters specified in Table 18.

TABLE18 URI query parameters supported by the POST method or this resource. Name Data type Description Qualifier n/a n/a n/a n/a

This method can support the request data structures specified in Table 19 and the response data structures and response codes specified in Table 20.

TABLE 19 Data structures supported by the POST Request Body on this resource. Data type Description SQ subscription- Details of the subscription to be created M RequestType

TABLE 20 Data structures supported by the POST Response Body on this resource. Response Data type codes Description SQ subscription- 201 In case of success the representation M ResponseType Created of the created subscription is returned. error- 4xx/5xx In case of failure the error object M ResponseType is returned.

HTTP DELETE can support the URI query parameters specified in Table 21.

TABLE 21 URI query parameters supported by the DELETE method on this resource. Name Data type Description Qualifier consumerReferenceId consumer- Identifies the M ReferenceId- consumer whose QueryType subscriptions shall be deleted

This method can support the response data structures and response codes specified in Table 22.

TABLE 22 Data structures supported by the DELETE Response Body on this resource. Response Data type codes Description SQ n/a 204 No In case of success no message n/a Content body is returned error- 4xx/5xx In case of failure the error M ResponseType object is returned. Resource “/subscriptions/{subscriptionId}””:

This resource represents a subscription.

The URI can be defined as follows:

Resource URI={DN_prefix_authority_part}/{DN_prefix_remainder}/PerfDataFileReportMnS/v1530/subscriptions/(subscriptionId)

Table 24 shows an example definition of resource URI variables.

TABLE 23 URI variables. Name Definition DN_prefix_authority_part See subclause 4.4 of TS 32.158 DN_refix_remainder See subclause 4.4 of TS 32.158 subscriptionId Subscription identifier

Http Methods:

HTTP DELETE can support the response data structures and response codes specified in table Table 24.

TABLE 24 Data structures supported by the DELETE Response Body on this resource Response Data type codes Description SQ n/a 204 No In case of success no message body M Content is returned error- 4xx/5xx In case of failure the error object M ResponseType is returned. Resource “/notificationSink”:

This resource represents a resource to which notifications are sent to.

The resource URI can be provided by the notification subscriber when creating the subscription.

Http Methods:

HTTP POST can support the request data structures specified in Table 25 and the response data structures and response codes specified in Table 26.

TABLE 25 Data structures supported by the POST Request Body on this resource. Data type Description SQ notifyFileReady-NotifType Type in case a notifyFileReady M notification is sent notifyFilePreparationError- Type in case a M NotifType notifyFilePreparationError notification is sent

TABLE 26 Data structures supported by the POST Response Body on this resource. Response Data type codes Description SQ n/a 204 No In case of success no message M Content body is returned error-ResponseType 4xx/5xx In case of failure the error object M is returned.

Example Data Type Definitions General Definitions

Table 27 shows example general data type definitions.

TABLE 27 Data types defined in this specification. Data type Reference Description General types dataTime-Type 11.3.1.1.4.6.2 Data type of date and time. uri-Type 11.3.1.1.4.6.2 The data type of a URI. Types used in paths Types used in query parts managementDataType-Type 11.3.1.1.4.6.3 Used in listing the information of available files describing the management data type of the files. consumerReferenceId- 11.3.1.1.4.6.2 Used in the query part of HTTP DELETE on /Subscriptions to QueryType delete all subscriptions made with a specific consumerReferenceId Types used in request bodies subscription-RequestType 11.3.1.1.4.4.1 Used in the request body of HTTP POST on /subscriptions to create performance data the reporting notifications subscriptions. Types used in response bodies fileInfoRetrieval-ResponseType 11.3.1.1.4.4.2 Used in the response body of HTTP GET describing the information of the listed files. error-ResponseType 11.3.1.1.4.4.3 Used in the response body describing the error. Types used for resources subscription-ResourceType 11.3.1.1.4.4.4 Representation of a subscription resource. Types used in notifications -NotifType 11.3.1.1.4.4.5 Used in the request body of HTTP POST for the notification type notifyFileReady. notifyFilePreparationError- 11.3.1.1.4.4.6 Used in the request body of HTTP POST for the notification NotifType type notifyFilePreparationError notifyFileReady. Types referenced by the definitions above fileInfo-Type 11.3.1.1.4.5.1 Used for describing the file information. notificationId-Type 11.3.1.1.4.6.2 Notification identifier as defined in ITU-T Rec. X. 733 notificationType-Type 11.3.1.1.4.6.4 Notification type (notifyFileReady, etc.) additionalText-Type 11.3.1.1.4.6.2 Allows a free form text description to be reported as defined in ITU-T Rec. X. 733 reason-Type 11.3.1.1.4.6.2 Used to describe the reason causing the file preparation error.

Example Query, Message Body and Resource Data Types:

An example definition for type subscription-RequestType are shown in Table 28.

TABLE 28 Definition of type subscription-RequestType Attribute name Data type Description SQ Data subscription-ResourceType Used in the request body of M HTTP POST on/subscriptions describing the representation of the subscription to be created

An example definition for type fileInfoRetrieval-ResponseType are shown in Table 29.

TABLE 29 Definition of type fileInfoRetrieval-ResponseType. Attribute name Data type Description SQ data array(fileInfoType) The information of the M available files

An example definition for type error-ResponseType are shown in Table 30.

TABLE 30 Definition of type error-ResponseType. Attribute name Data type Description SQ error object Key indicating the response body M containing an error > errorinfo string Attribute allowing to convey error M information in string format

An example definition for type subscription-ResourceType is shown in Table 31.

TABLE 31 Definition of type subscription-ResourceType. Attribute name Data type Description SQ consumerReference uri-Type The URI of the endpoint to send M the notification to (/notificationSink). timeTick long- Time window within which the O Type subscriber intends to subscribe again to confirm its subscription, see clause 6.2.2.5.1 filter filter- Filter settings for this subscription, O Type to define the subset of all notifications this subscription relates to. A notification is sent to the subscriber if the filter matches, or if there is no filter.

An example definition for type notifyFileReady-NotifType is shown in Table 32.

TABLE 32 Definition of type notifyFileReady-NotifType. Attribute name Data type Description SQ header > href uri-Type URI of the resource indicating M the performance data file reporting service > notificationId notificationId- Notification identifier as M Type defined in ITU-T Rec. X. 733 > notificationType notificationType- Notification type Type (notifyFileReady, etc.) > eventTime dateTime-Type Event occurrence time (e.g., M the file ready time) body > fileInfoList array(fileInfo- The information of the M Type) available files > additionalText additionalText- Allows a free form text O Type description to be reported as defined in ITU-T Rec. X. 733

An example definition for type notifyFilePreparationError-NotifType is shown in Table 33.

TABLE 33 Definition of type notifyFilePreparationError-NotifType. Attribute name Data type Description SQ header > href uri-Type URI of the resource indicating M the performance data file reporting service > notificationId notificationId- Notification identifier as Type defined in ITU-T Rec. X. 733 > notificationType notificationType- Notification type M Type (notifyFileReady, etc.) > eventTime dateTime-Type Event occurrence time M (e.g., the file ready body time) > fileInfoList array(fileInfo- The information of the M Type) available files > reason reason-Type The reason that caused the error of the file preparation. > additionalText additionalText- Allows a free form text O Type description to be reported as defined in ITU-T Rec. X. 733

Example Referenced Structured Data Types

An example definition of type fileInfo-Type is shown in Table 34.

TABLE 34 Definition of fileInfo-Type. Attribute name Data type Description SQ fileLocation uri-Type Usd to indicate the location M of the file. fileSize long-Type The size of the file with positive Integer value (the unit is byte). fileReadyTime dataTime- Indicates the date and time when M Type the file was last closed and made available in the management service producer and the file content will not be changed. fileExpirationTime dataTime- Indicates the date and time beyond M Type which the file may be deleted. fileCompression string Identifies the name of the M compression algorithm used for the file. fileFormat string Identifies the encoding technique M used by the file. Its value should indicate the version of the file format specification plus to indicate if “ASN1” or “XML-schema” is used.

Example Simple Data Types and Enumerations:

This section defines simple data types and enumerations that can be used by the data structures defined in the previous sections.

Table 35 shows example simple data types.

TABLE 35 Simple data types. Type Type name definition Description dataTime-Type string The data type for date and time in “date-time” format. uri-Type string The type of a URI. consumerReferenceId- uri-Type Used in the query part of HTTP QueryType DELETE on /subscriptions to delate all subscriptions made with a specific consumerReferenceId. filter-Type string Filter of a subscription resource. notificationId-Type long Notification identifier as defined in ITU-T Rec. X. 733 additionalText-Type string Allows a free form text description to be reported as defined in ITU-T Rec. X. 733 reason-Type string THe type for describing the reason that caused the file preparation error.

An example enumeration of managementDataType-Type is shown in Table 36.

TABLE 36 Enumeration managementDataType-Type. Enumeration value Description PM It indicates that the management data the type is “PM”

An example enumeration of notificationType-Type is shown in Table 37.

TABLE 37 Enumeration notificationType-Type. Enumeration value Description notifyFileReady Notification type is notifyFileReady notifyFilePreparationError Notification type is notifyFilePreparationError

OpenAPI Specification

This section describes the example capabilities of the Management Services in the structure of the OpenAPI Specification Version 3.0.1. The OpenAPI document is represented in the JSON format option.

Example code is provided below.

Example Performance Threshold Monitoring Service Example Mapping of Commands Between a “Server Sent” Protocol and an “In-Sync” Protocol:

In some implementations, performance threshold monitoring operations that were previously performed using a half-duplex communications channel (e.g., according to “server sent” protocol, such as HTTP) can be instead performed using a full-duplex communications channel (e.g., according to an “in-sync” (IS) protocol, such as WebSocket). Example mappings of SS commands to IS commands are detailed below.

The IS notifications can be mapped to SS equivalents according to Table 38.

TABLE 38 Mapping of IS notifications to SS equivalents. IS notifications HTTP Method Resource URI SQ notifyThresholdCrossing POST /notificationSink M

For the notification “notifyThresholdCrossing,” the IS notification parameters can be mapped to SS equivalents according to Table 39.

TABLE 39 Mapping of IS notification input parameters to SS equivalents (HTTP POST). IS operation SS SS SS parameter parameter parameter parameter name location name type SQ objectClass request href uri-Type M objectInstance body notificationId request notificationId notificationId-Type M body eventTime request eventTime dateTime-Type M body notificationType request notificationType notificationType-Type M body startOfMonitoringGP request startOfMonitoringGP dateTime-Type M body endOfMonitoringGP request endOfMonitoringGP dateTime-Type M body monitoredObjectInstance request monitoredObjectInstance uri-Type body thresholdLevel request thresholdLevel thresholdLevel-Type M body measurementTypeName request measurementTypeName measurementTypeName-Type M body measurementValue request measurementValue measurementValue-Type M body additionalText request additionalText additionalText-Type O body

Example Resources Structures

Table 40 provides an overview of example resources and applicable HTTP methods.

TABLE 40 Resources and methods overview. Resource Resource HTTP name URI method Description notificationSink /notificationSink POST Send notifications

Example Resource Definitions

Resource “/notificationSink”:

This resource represents a resource to which notifications are sent to.

The resource URI can be provided by the consumer when creating the threshold monitor (via the monitoringNotifTarget attribute of the MOI ThresholdMonitor, see 3GPP TS 28.622).

Http Methods:

HTTP POST can support the request data structures specified in Table 41 and the response data structures and response codes specified in Table 42.

TABLE 41 Data structures supported by the POST Request Body on this resource Data type Description SQ notifyThresholdCrossing-NotifType Type in case a notifyThresholdCrossing M notification is sent

TABLE 42 Data structures supported by the POST Response Body on this resource. Data type Response codes Description SQ n/a 204 No Content In case of success no message body is returned M error-ResponseType 4xx/5xx In case of failure the error object is returned. M

Example Data Type Definitions General Definitions

Table 43 shows example general data type definitions.

TABLE 43 Data types defined in this specification. Data type Reference Qualifier General types dataTime-Type 11.3.1.2.4.6.2 Data type of date and time. uri-Type 11.3.1.2.4.6.2 The data type of a URI. Types used in paths Types used in query parts Types used in request bodies Types used in response bodies error-ResponseType 11.3.1.2.4.4.3 Used in the response body describing the error. Types used for resources Types used in notifications notifyThresholdCrossing- 11.3.1.2.4.4.5 Used in the request body of HTTP POST for NotifType the notification type notifyThresholdCrossing. Types referenced by the definitions above notificationId-Type 11.3.1.2.4,6.2 Notification identifier as defined in ITU-T Rec. X. 733 notificationType-Type 11.3.1.2.4.6.3 Notification type (notifyThresholdCrossing, etc.) thresholdLevel-Type 11.3.1.2.4.6.2 Threshold level type measurementTypeName-Type 11.3.1.2.4.6.2 Measurement name defined in the performance measurements TS (e.g., TS 28.552) measurementValue-Type 11,3,1.2.4.6.2 Measurement value type additionalText-Type 11.3.1.2.4.6.2 Allows a free form text description to be reported as defined in ITU-T Rec. X. 733

Example Query, Message Body and Resource Data Types:

An example definition for type error-ResponseType is shown in Table 44.

TABLE 44 Definition of type error-ResponseType. Attribute name Data type Description SQ Error object Key indicating the response body M containing an error >errorInfo string Attribute allowing to convey error M information in string format

Example Referenced Structured Data Types:

An example definition of type notifyThresholdCrossing-NotifType is shown in Table 45.

TABLE 45 Definition of notifyThreshol dCrossing-NotifType. Attribute name Data type Description SQ header >href un-Type URI of the resource indicating the M performance threshold monitoring service >notificationId notificationId-Type Notification identifier as defined in M ITU-T Rec. X. 733 >notificationType notificationType-Type Notification type (notifyFileReady, etc.) M >eventTime dateTime-Type Event occurrence time (e.g.; the M file ready time) body >startOfMonitoringGP dateTime-Type Time stamp of the start of monitoring GP M >endOfMonitoringGP dateTime-Type Time stamp of the end of monitoring GP M >monitoredObjectInstance uri-Type URI of the monitored object instance M >thresholdLevel thresholdLevel-Type Threshold level that has been reached M or crossed >measurementTypeName measurementTypeName- The measurement name whose value has M Type reached or crossed the threshold >measurementValue measurementValue-Type The measurement value that reached or M crossed the threshold >additionalText additionalText-Type Allows a free form text description to be M reported as defined in ITU-T Rec. X. 733

Example Simple Data Types and Enumerations:

This section defines simple data types and enumerations that are used by the data structures defined in the previous sections.

Table 46 shows example simple data types.

TABLE 46 Simple data types. Type Type name definition Description dataTime-Type string The data type for date and time in “date-time” format. uri-Type string The type of a URI. notificationId-Type long Notification identifier as defined in ITU-T Rec. X. 733 thresholdLevel-Type integer The type of threshold level. measurementTypeName-Type string The measurement name defined in the performance measurements TS (e.g,, TS 28.552) measurementValue-Type string The string converted from measurement value type defined in the performance measurements TS (e.g., TS 28.552) additionalText-Type string Allows a free form text description to be reported as defined in ITU-T Rec. X. 733

An example enumeration of notificationType-Type is shown in Table 47.

TABLE 47 Enumeration notificationType-Type. Enumeration value Description notifyThresholdCrossing Notification type is notifyThresholdCrossing

OpenAPI Specification

This section describes the capabilities of the Management Services in the structure of the OpenAPI Specification Version 3.0.1. The OpenAPi document is represented in the JSON format option.

Example code is provided below.

{  “openapi”: “3.0.1”,  “info”: {   “title”: “TS 28.532 Performance Threshold Monitoring Service”,   “version”: “16.1.0”,   “description”: “OAS 3.0.1 specification of the Performance Threshold Monitoring Service”  },  “servers”: [   {    “url”: “http://{monitoringNotifTarget}”,    “variables”: {     “monitoringNotifTarget”: {      “description”: “The open API server of the performance threshold monitoring service is located in the consumer side, see monitoringNotifTarget attribute of the IOC ThresholdMonitor defined in 3GPP TS 28.622. ”,      “default”: “example.com”     }    }   }  ],  “paths”: {   “/notificationSink”: {    “post”: {     “summary”: “Send notifications about performance threshold crossing”,     “description”: “To send a notifyThresholdCrossing notification”,     “requestBody”: {      “required”: true,      “content”: {       “application/json”: {        “schema”: {         “$ref”: “#/components/schemas/notifyThresholdCrossing-NotifType”        }       }      },      “responses”: {       “204”: {        “description”: “Success case (\“204 No Content\”). The notification is successfully delivered. The response message body is absent.”       },       “default”: {        “description”: “Error case.”,        “content”: {         “application/json”: {        “schema”: {         “$ref”: “#/components/schemas/error- ResponseType”        }       }      }     }    }   }  } }, “components”: {  “schemas”: {   “dateTime-Type”: {    “type”: “string”,    “format”: “date-Time”   },   “uri-Type”: {    “type”: “string”   },   “long-Type”: {    “type”: “string”,    “format”: “long”   },   “thresholdLevel-Type”: {    “type”: “integer”   },   “measurementTypeName-Type”: {    “type”: “string”   },   “measurementValue-Type”: {    “type”: “string”   },   “additionalText-Type”: {    “type”: “string”   },   “error-ResponseType”: {    “type”: “object”,    “properties”: {    “error”: {     “type”: “object”,     “properties”: {      “errorInfo”: {       “type”: “string”      }     }    }   }  },  “header-Type”: {   “description”: “Header used in notifications as notification header”,   “type”: “object”,   “properties”: {    “uri”: {     “$ref”: “#/components/schemas/uri-Type”    },    “notificationId”: {     “$ref”: “#/components/schemas/notificationId- Type”    },    “notificationType”: {     “$ref”: “#/components/schemas/notificationType-Type”    },    “eventTime”: {     “$ref”: “#/components/schemas/dateTime-Type”    }   }  },  “notifcationId-Type”: {   “$ref”: “#/components/schemas/long-Type”  },  “notificationType-Type”: {   “type”: “string”,   “enum”: [    “notifyThresholdCrossing”   ]  },  “notifyThresholdCrossing-NotifType”: {   “type”: “object”,   “properties”: {    “header”: {     “$ref”: “#/components/schemas/header-Type”   },   “body”: {   “type”: “object”,   “properties”: {    “startOfMonitoringGP”: {     “$ref”: “#/components/schemas/dateTime- Type”    },    “endOfMonitoringGP”: {     “$ref”: “#/components/schemas/dateTime- Type”    },    “monitoredObjectInstance”: {     “$ref”: “#/components/schemas/uri-Type”    },    “thresholdLevel”: {     “$ref”: “#/components/schemas/thresholdLevel-Type”    },    “measurementTypeName”: {    “$ref”: “#/components/schemas/measurementTypeName-Type”    },    “measurementValue”: {     “$ref”: “#/components/schemas/measurementValue-Type”    },    “additionalText”: {     “$ref”: “#/components/schemas/additionalText-Type”     }    }    }   }   }  }  } }

The disclosure herein makes reference to 3GPP TS 28.550; 3GPP TS 28.552; 3GPP TS 28.554; 3GPP TS 28.622; 3GPP TS 32.158; 3GPP TS 32.425; ITU-T Recommendation X.733 (02/92): “Information technology—Open Systems Interconnection—Systems Management: Alarm reporting function,” ITU-T Recommendation X.680 (08/2015) “Information Technology—Abstract Syntax Notation One (ASN.1): Specification of basic notation” (same as the ISO/IEC International Standard 8824-1); ITU-T Recommendation X.681 (08/2015) “Information Technology—Abstract Syntax Notation One (ASN.1): Information object specification” (Same as the ISO/IEC International Standard 8824-2); ITU-T Recommendation X.691 (08/2015) “Information technology—ASN.1 encoding rules: Specification of Packed Encoding Rules (PER)” (Same as the ISO/IEC International Standard 8825-2); IETF RFC 6455: “The WebSocket Protocol”; IETF RFC 2616: “Hypertext Transfer Protocol—HTTP/1.1”; IETF RFC 793: “TRANSMISSION CONTROL PROTOCOL”; IETF RFC 5234: “Augmented BNF for Syntax Specifications: ABNF”; and IETF RFC 3986: “Uniform Resource Identifier (URI): Generic Syntax.” The contents of each of these technical specifications is incorporated by reference in their entirety.

For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below. For example, the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.

It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.

The methods described here may be implemented in software, hardware, or a combination thereof, in different implementations. In addition, the order of the blocks of the methods may be changed, and various elements may be added, reordered, combined, omitted, modified, and the like. Various modifications and changes may be made as would be obvious to a person skilled in the art having the benefit of this disclosure. The various implementations described here are meant to be illustrative and not limiting. Many variations, modifications, additions, and improvements are possible. Accordingly, plural instances may be provided for components described here as a single instance. Boundaries between various components, operations and data stores are somewhat arbitrary, and particular operations are illustrated in the context of specific illustrative configurations. For purposes of explanation and not limitation, specific details are set forth such as particular structures, architectures, interfaces, techniques, etc. in order to provide a thorough understanding of the various aspects of various embodiments. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of the present document, the phrase “A or B” means (A), (B), or (A and B). Other allocations of functionality are envisioned and may fall within the scope of claims that follow. Any of the above-described examples may be combined with any other example (or combination of examples), unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments. 

1.-39. (canceled)
 40. A system comprising: one or more processors; and memory storing instructions that when executed by the one or more processors, cause the one or more processors to perform operations comprising: sending, by a management service (MnS) producer, a first request to establish a connection for streaming performance data regarding a wireless communications network to a MnS consumer, wherein the first request comprises a Hypertext Transfer Protocol (HTTP) GET command, the GET command comprising (i) an request to upgrade the connection from an HTTP connection to a WebSocket connection, and (ii) a plurality of parameters associated with one or more units of performance data to be streamed using the connection, wherein the plurality of parameters comprises: an identifier for a data stream comprising the one or more units of performance data, an indication of one or more measurements types of the one or more units of performance data, and an indication of a domain name associated with the one or more units of performance data; receiving, by the MnS producer, a first response from the MnS consumer confirming establishment of the connection; transmitting, by the MnS producer using the connection, the data stream comprising the one or more units of performance data to the MnS consumer, the one or more units comprising one or more performance metrics regarding the wireless communications network; sending, by the MnS producer, a second request to the MnS consumer to terminate the connection; and receiving, by the MnS producer, a second response from the MnS consumer confirming termination of the connection.
 41. The system of claim 40, wherein the one or more performance metrics comprise at least one of: a latency associated with at least a portion of the wireless communications network, a throughput associated with at least the portion of the wireless communications network, a number of registered subscribers for at least the portion of the wireless communications network, a number of established network sessions for at least the portion of the wireless communications network, or an energy efficiency of at least the portion of the wireless communications network.
 42. The system of claim 41, wherein the one or more performance metrics comprise at least one of: a number of attempts to perform a particular operation with respect to at least a portion of the wireless communications network, a number of successful attempts to perform the particular operation with respect to at least the portion of the wireless communications network, or a number of unsuccessful attempts to perform the particular operation with respect to at least a portion of the wireless communications network.
 43. The system of claim 40, wherein the plurality of parameters associated with the one or more units of performance data to be streamed using the connection are encapsulated in a Query portion of a Request-Line of the HTTP GET command.
 44. The system of claim 40, wherein transmitting the data stream comprises transmitting a plurality of WebSocket Data frames in a sequence, wherein the one or more units of performance data are included in payload data of the plurality of WebSocket Data frames, and wherein payload data is encoded according to Abstract Syntax Notation One (ASN.1).
 45. The system of claim 44, wherein at least one of the plurality of WebSocket Data frames is encoded such that a bit string value is placed in a bit-field, wherein a leading bit of the bit string value is placed in a leading bit of the bit-field, and wherein a trailing bit of the bit string is placed in a trailing bit of the bit-field.
 46. The system of claim 40, wherein at least one of the second request or the second response comprises a WebSocket Close frame.
 47. The system of claim 40, wherein the operations further comprise: receiving, by the MnS producer, a subscription request from a second MnS consumer, and subsequent to receiving the subscription request, transmitting, by the MnS producer, one or more notifications to the second MnS consumer according to the subscription request, the one or more notifications comprising one or more second performance metrics regarding the wireless communications network.
 48. The system of claim 47, wherein the notification is transmitted using a HTTP POST command.
 49. The system of claim 47, wherein the subscription request comprises an indication of a threshold value with respect to the one more second performance metrics, and wherein the one or more notifications are transmitted responsive to the one more second performance metrics crossing the threshold value.
 50. A method comprising: sending, by a management service (MnS) producer, a first request to establish a connection for streaming performance data regarding a wireless communications network to a MnS consumer, wherein the first request comprises a Hypertext Transfer Protocol (HTTP) GET command, the GET command comprising (i) an request to upgrade the connection from an HTTP connection to a WebSocket connection, and (ii) a plurality of parameters associated with one or more units of performance data to be streamed using the connection, wherein the plurality of parameters comprises: an identifier for a data stream comprising the one or more units of performance data, an indication of one or more measurements types of the one or more units of performance data, and an indication of a domain name associated with the one or more units of performance data; receiving, by the MnS producer, a first response from the MnS consumer confirming establishment of the connection; transmitting, by the MnS producer using the connection, the data stream comprising the one or more units of performance data to the MnS consumer, the one or more units comprising one or more performance metrics regarding the wireless communications network; sending, by the MnS producer, a second request to the MnS consumer to terminate the connection; and receiving, by the MnS producer, a second response from the MnS consumer confirming termination of the connection.
 51. The method of claim 50, wherein the one or more performance metrics comprise at least one of: a latency associated with at least a portion of the wireless communications network, a throughput associated with at least the portion of the wireless communications network, a number of registered subscribers for at least the portion of the wireless communications network, a number of established network sessions for at least the portion of the wireless communications network, or an energy efficiency of at least the portion of the wireless communications network.
 52. The method of claim 50, wherein the one or more performance metrics comprise at least one of: a number of attempts to perform a particular operation with respect to at least a portion of the wireless communications network, a number of successful attempts to perform the particular operation with respect to at least the portion of the wireless communications network, or a number of unsuccessful attempts to perform the particular operation with respect to at least a portion of the wireless communications network.
 53. The method of claim 50, wherein the plurality of parameters associated with the one or more units of performance data to be streamed using the connection are encapsulated in a Query portion of a Request-Line of the HTTP GET command.
 54. The method of claim 50, wherein transmitting the data stream comprises transmitting a plurality of WebSocket Data frames in a sequence, wherein the one or more units of performance data are included in payload data of the plurality of WebSocket Data frames, and wherein payload data is encoded according to Abstract Syntax Notation One (ASN.1).
 55. The method of claim 54, wherein at least one of the plurality of WebSocket Data frames is encoded such that a bit string value is placed in a bit-field, wherein a leading bit of the bit string value is placed in a leading bit of the bit-field, and wherein a trailing bit of the bit string is placed in a trailing bit of the bit-field.
 56. The method of claim 50, wherein at least one of the second request or the second response comprises a WebSocket Close frame.
 57. The method of claim 50, further comprising: receiving, by the MnS producer, a subscription request from a second MnS consumer, and subsequent to receiving the subscription request, transmitting, by the MnS producer, one or more notifications to the second MnS consumer according to the subscription request, the one or more notifications comprising one or more second performance metrics regarding the wireless communications network.
 58. The method of claim 57, wherein the notification is transmitted using a HTTP POST command.
 59. The method of claim 57, wherein the subscription request comprises an indication of a threshold value with respect to the one more second performance metrics, and wherein the one or more notifications are transmitted responsive to the one more second performance metrics crossing the threshold value. 